I need an alternate approach that i think can be achieved via mod_rewrite and session ID to control the dynamic creation of webpages based on the entrance URL
basically, when a user goes to the website, [url removed, login to view] VS. a 'private' domain (masked url) such as [url removed, login to view] ..a cookie is set detecting the entrance URL.
This is then utilized to hide/mask the feature 'locate a doctor' -- appearing on the top header of the site and on the left-hand menu of the site..if and only if..you enter the site via [url removed, login to view]
if you enter via a masked url/ (private doc's site)...since it is supposed to be for their use only - -we hide the buttons for locate a doctor
I need to change how this is occuring now to utlize modrewrite / session id, i guess:
here is the feedback i rec'd on what needs to be done:
mod_perl, rather or using mod_rewrite?
That way, the URLs can be modified regardless of the type of page (html, php, perl, etc).
Using mod_rewrite, this behavior can only be approximated by rewriting (i.e. redirecting) all URLs to a backend engine that does its best to deliver the modified page contents.
For HTML pages, it's simply a matter of reading the page, which doesn't present much of a problem. However, for scripted pages (perl, php, etc), the best way to obtain the page contents is to actually load the page from the server so that the server can handle the scripted portions.
In order to approximate this behavior using mod_rewrite, a special flag would have to be passed to the server indicating that a page should be presented as-is. Then, when rendering dynamic pages (php, perl, etc), the backend could append this flag to the URL, retrieve the page as it would be served normally, and then modify the links to include the session ID. In other words, behind the scenes, if a user were to load a perl script located at [url removed, login to view], the behavior using mod_rewrite would be as follows:
[url removed, login to view] redirects to [url removed, login to view] (user still sees [url removed, login to view] in their location bar. [url removed, login to view] is invisible).[url removed, login to view] requests [url removed, login to view] from web server with special "do not modify" tag appended [url removed, login to view] receives unaltered [url removed, login to view], modifies it to include session IDs [url removed, login to view] sends altered [url removed, login to view] to user's browser
It all boils down to the entrance URL (usually a masked domain name)
(1) it controls the 'home' button
(2) it hides/reveals the locate a doctor button on the left
(3) it hides/reveals the locate button up top
(4) is also tied to this concept of 'sticking' to the original entrance page's menu set up
The problem occurs when users access the site from aol/isp's using proxies.
I am currently using a shared server on [url removed, login to view] with domain masking via godaddy.
I need 100% superb docuementation, installation, testing.
Ideally i would have a result allowing me to have a more modular / dynamically created website.
At the very least, the menu function as it works now-- needs to work despite ISP PROXY scenarios such as AOL.
The website is live now and must continue to be work as it is, until completely tested with new script. i can provide several domain redirects to test .html pages