On Nov 11, 2007, at 11:24, Fastream Technologies wrote:
> Ok. We have a URL rewrite part in our IQ reverse proxy (
> http://www.fastream.com/iqreverseproxy.php) but not for the web
> server. Just
> wondered if there was an easier way to do it.
Maybe like Francois suggested: to extract meaning at the application
level. But I think it wouldn't be that hard to expose an event at the
moment the request is received, right before doing anything else, and
give the application, or any other module, the chance to "re-write" it
into a query-string. Then, whatever is returned by this event becomes
the de factor URL as if it came from the client, completely discarding
the original version.
This is how ASP.NET (and I think some Java application servers) does
it. The idea is to use the query-string mechanism since the rest of
the web server and the application already are aware of this, instead
of having to create a new "environment" and data structure system for
each particular usage.
If triggered as an event, or exposed to external modules somehow, then
each application can make its on re-writer as complex as it needs to,
but the server doesn't need to care.
dZ.
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
