Forum Discussion
Lucas_Thompson_
Nov 10, 2015Historic F5 Account
You're likely encountering bug ID 428268, documented here:
http://support.f5.com/kb/en-us/solutions/public/15000/400/sol15445.html
If you like, you can submit a request to Support to get a build with the fix for it. This issue is not resolved in any release or hotfix yet. Note that the trailing ampersand probably isn't required by the web server (it's the CGI delimiter) so you could probably just get rid of it. You could work around it by using an irule like this on your virtual:
workaround for F5 bug ID 428268
if the URI has unusual format in CGI parameters (trailing ampersand), fix it up
when CLIENT_ACCEPTED {
ACCESS::restrict_irule_events disable
}
when HTTP_REQUEST {
if { [HTTP::uri] ends_with "&" } {
log local0. "Redirecting user to get rid of ampersand"
HTTP::respond 302 Location [string range [HTTP::uri] 0 "end-1"]
}
}
- Vinne73Nov 12, 2015CirrusYes this seems to be my problem. The "Applies to" needs to be updated because I run on 11.6. I guess the problem is not fixed yet. About the problem: it should be none of the BigIP's business what the Original URL is, and if it's properly formatted or not but that's just my opinion ;)
- Lucas_Thompson_Nov 12, 2015Historic F5 AccountIt's an acknowledged defect and will be fixed shortly. The system must parse this URI value because it's transformed into two different forms of redirect URL, one for the end policy redirect and one for the 302 multidomain bounce-back cookie setting implementation. It's just that the parser isn't flexible enough to parse unparsable things where the values don't conform to the CGI specification in RFC 3875.