[AOLSERVER] We've made a code change, would like opinions as to is this a good or bad idea...

2001-12-07 Thread Greg Wolff
At BNA we have a problem with use of AOLserver in terms of how it handles the Location parameter value. The Location is a fixed value that is a global constant for the AOLserver process. In our virtual hosting environment on our production machines this a problem. The problem is as follows:

Re: [AOLSERVER] We've made a code change,

2001-12-07 Thread Jim Wilcoxson
I'm confused. Browsers are supposed to handle relative URL redirection, so I don't understand why a relative redirect is being changed to absolute by this routine. If it were just kept relative (i.e., original code was removed instead of adding new code), then relative redirect requests could

Re: [AOLSERVER] We've made a code change,

2001-12-07 Thread Rob Mayoff
+-- On Dec 7, Jim Wilcoxson said: I'm confused. Browsers are supposed to handle relative URL redirection, No, they're not. Some (including IE and Mozilla, I believe) do handle relative URLs, but the HTTP/1.1 standard requires the Location header to contain an absolute URL.

Re: [AOLSERVER] We've made a code change,

2001-12-07 Thread Dossy
On 2001.12.07, Jim Wilcoxson [EMAIL PROTECTED] wrote: I'm confused. Browsers are supposed to handle relative URL redirection, They are? You're right; you're confused. Perhaps browsers _do_ support relative URL redirection because so many people have foolishly violated the HTTP/0.9, HTTP/1.0

Re: [AOLSERVER] We've made a code change, would like opinions as to is this a good or bad idea...

2001-12-07 Thread Dossy
On 2001.12.07, Peter M. Jansson [EMAIL PROTECTED] wrote: The only concern I have is a security concern I looked at security as a possibility as well and since his solution uses DStrings (which are growable, right?) then you don't have to necessarily worry about buffer overflow. However,

Re: [AOLSERVER] We've made a code change, would like opinions as to is this a good or bad idea...

2001-12-07 Thread Rob Mayoff
+-- On Dec 7, Dossy said: However, resource starvation/denial of service is a serious potential problem. Fire up a couple hundred connections where you feed a very large Host: string ... On the contrary, AOLserver limits both the size of each HTTP header line (default 8192 bytes),

Re: [AOLSERVER] We've made a code change,

2001-12-07 Thread Jim Wilcoxson
However, resource starvation/denial of service is a serious potential problem. Fire up a couple hundred connections where you feed a very large Host: string ... Go to any web site and hit its search engine 200 times. It will most likely die a horrible death. In fact, any routine request to

Re: [AOLSERVER] We've made a code change, would like opinions as to is this a good or bad idea...

2001-12-07 Thread Dossy
On 2001.12.07, Rob Mayoff [EMAIL PROTECTED] wrote: +-- On Dec 7, Dossy said: However, resource starvation/denial of service is a serious potential problem. Fire up a couple hundred connections where you feed a very large Host: string ... On the contrary, AOLserver limits both