Can you get banned from Google for this? I seem to remember they want to be
served exactly the same content that a regular useragent would get.
Obviously this isn't the kind of stuff they're trying to avoid... Just
wondering.

On 6/15/06, Jeff Lubetkin <[EMAIL PROTECTED]> wrote:

You can prevent JSESSIONID from being encoded onto URLs for bots.  At
Zillow, we've done this with a ServletFilter that compares the incoming
user agent to a list of known bots, and if it matches replaces the
HttpServletResponse with an HttpServletResponseWrapper that makes the
encodeURL, encodeUrl, encodeRedirectURL, and encodeRedirectUrl methods
into no-ops (simply returning their inputs).

jeff

Reply via email to