On Wednesday, September 7, 2011 1:04:59 PM UTC+2, maq wrote: > > Hi, Thomas, > > I learned a lot from your latest answer. Thanks! > > caniuse.com's approach is exactly what I want. Can you give more details > on how the redirecting is done for the comment below? > "So redirecting from /foo to #foo might be better (caniuse.com does just > that: redirect /history to #feat=history) "? >
Can't you use Firebug or the Chrome Developer Tools (or anything else) to look at the HTTP traffic and/or HTML response? It actually looks like I was wrong about "caniuse", it doesn't do redirects; but Twitter does redirect from, say https://twitter.com/tbroyer to https://twitter.com/#!/tbroyer (when logged in). They simply use an HTTP redirect (sendRedirect() in servlet parlance). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/cLY0bRNogr8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
