The reason I don't do a 302 is I don't want the browser's address bar to change + for SEO.
>-----Original Message----- >From: Igor Vaynberg [mailto:[email protected]] >Sent: Saturday, 22 October 2011 5:52 PM >To: [email protected] >Subject: Re: Forwarding in 1.5 not working like in 1.4 > >this is a general problem with forwarding. instead of forwarding why >dont you just 302? > >-igor > >On Fri, Oct 21, 2011 at 11:33 PM, Chris Colman ><[email protected]> wrote: >> I've just noticed that some of the .js resources seem to be loading from >> different addresses. I'm using 1.5.2 with the UrlRenderer patch to fix >> the forwarding issue. >> >> Depending on the page it appears like the same .js is requested at two >> different URLs. Presumably the browser will perform a download each time >> as it will cache each differently according to their different URLs. >> >> >> servlet path: >> /content/home/wicket/resource/org.apache.wicket.markup.html.WicketEventR >> eference/wicket-event-ver-1319264330000.js >> >> /wicket/resource/org.apache.wicket.markup.html.WicketEventReference/wick >> et-event-ver-1319264330000.js >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
