tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: SCRIPT_NAME and PATH_INFO with extension mapping
Date Mon, 01 Oct 2001 02:07:54 GMT
Actually, Google is one of the few sites that do cache pages with query
strings (try searching for "tmwx" if you don't believe me).
----- Original Message -----
From: "Jon Stevens" <jon@latchkey.com>
To: "tomcat-dev" <tomcat-dev@jakarta.apache.org>
Sent: Sunday, September 30, 2001 6:37 PM
Subject: Re: SCRIPT_NAME and PATH_INFO with extension mapping


> on 9/30/01 7:16 PM, "cmanolache@yahoo.com" <cmanolache@yahoo.com> wrote:
>
> > 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
>
> The implications of this are HUGE though and it really needs to be fixed
> back. It essentially means that it is impossible to use suffix mapping in
> order to have a searchable website. In other words, Google.com doesn't
cache
> websites with a "?" in the URL. If we can't pass GET parameters via
> PATH_INFO, then where/how can we pass this information around?
>
> -jon
>
>


*----*

This message is intended only for the use of the person(s) listed above 
as the intended recipient(s), and may contain information that is 
PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, 
you may not read, copy, or distribute this message or any attachment.  
If you received this communication in error, please notify us immediately 
by e-mail and then delete all copies of this message and any attachments.


In addition you should be aware that ordinary (unencrypted) e-mail sent 
through the Internet is not secure. Do not send confidential or sensitive 
information, such as social security numbers, account numbers, personal 
identification numbers and passwords, to us via ordinary (unencrypted) 
e-mail. 

Mime
View raw message