On Sun, 30 Sep 2001, Jon Stevens wrote: > on 9/30/01 5:47 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > the conclusion was that the HTTP spec is wrong and we should > > follow the Servlet spec. > > That is complete BS. The servlet spec shouldn't 'override' what is defined > in the HTTP spec unless absolutely necessary. This is definitely not a > necessary case, but instead an act of stupidity. > > > Workaround - declare each page with exact mappings in web.xml. > > Making me specify each and every page in my webapp in the web.xml is just > plain BS. > > I bet that a URL like this works: > > http://www.foo.com/MicrosoftIsBetterThanSun.asp/foo/bar > > I *know* that this URL works: > > http://www.foo.com/PHPIsBetterThanJSP.php/foo/bar > > Essentially, what you are doing by removing this capability is preventing > the SCRIPT_NAME from having PATH_INFO and that is not right according to the > HTTP spec. I don't think that a Servlet container can override the behavior > of the HTTP spec and still claim HTTP compliance.
Well, I agree with you - but I feel ofended by the 'you' in this phrase. I didn't removed it - I spent quite a bit of time and arguments to keep it in. BTW, it has nothing to do with the HTTP spec ( which doesn't specify anything like that), but with the way all known web servers operate. And it has nothing to do with JSPs as well - it's true for any extension mapped servlets. Costin
