Cool, thanks for the info. I'll probably be going the same route. Should our site get banned, I'll alert the list ;-)
On 6/16/06, Jeff Lubetkin <[EMAIL PROTECTED]> wrote:
We've noticed no issues, and SEO experts that we've talked to support this mechanism. Of course, Google being Google there's no way to know for sure what they do or don't like... jeff -----Original Message----- From: D&J Gredler [mailto:[EMAIL PROTECTED] Sent: Friday, June 16, 2006 4:24 AM To: Tapestry users Subject: Re: Remove jsessionid from static resources? 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
