Just a thought:

as part of the info an HTTPRequest provides, how about a
method like "isSecure" or similar? I'm currently doing this
as a servlet method, which checks the request env variables
for port 443 or the envvar SERVER_PORT_SECURE is 1 (i think
this one is IIS specific..)

Anyways. There's one of the problems with this idea: I
don't know of any standard way to determine whether a
request is secure. But it just makes more sense to me that
this be part of the request if possible.

I remember it being mentioned a while ago that it might be
possible for site-specific subclasses of Session, request,
etc to be used (rather than directly modifying a webware
install). Any progress, word on this?

Cool, have fun,

Luke

=====
------------------
Reference Counting Garbage Collection:
Look out philosophy majors, things really DO
cease to exist when no one is looking at them!
------------------

__________________________________________________
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards�
http://movies.yahoo.com/

_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to