[
https://issues.apache.org/jira/browse/WICKET-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831492#action_12831492
]
Sebb commented on WICKET-2732:
------------------------------
Minor correction - JMeter works fine, it follows the redirect, but does not
convert the location.
The location appears to be an absolute URL, so is not converted by the call to
java.net.URL.URL(URL context, String spec) .
[JMeter calls this with the spec set to the Location: reference]
Indeed some OSes may permit "." as a file name, so this AFAICS is the correct
behaviour by JMeter.
Wicket should ideally return a valid absolute URL, failing that it should
return a valid relative URL.
The current behaviour appears to be neither.
> Wicket redirects don't work with Apache JMeter
> ----------------------------------------------
>
> Key: WICKET-2732
> URL: https://issues.apache.org/jira/browse/WICKET-2732
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.6
> Environment: Glassfish
> Reporter: Alexander Fisher
>
> Unlike some browsers, JMeter does not fix up the broken URLs returned in the
> Location header of 302 redirects generated by wicket.
> For instance, after signing out of a wicket 1.4.6 app, the redirect might be
> to Location: http://host/wicket-app/.
> Some browsers and even some webservers will fix this up (removing the dot),
> but JMeter will not and glassfish (and possibly other appservers) will return
> a 404 error.
> I've have discussed the issue with the JMeter developer and hence opened this
> ticket.
> http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-user/201002.mbox/browser
> Many thanks,
> Alex
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
