Your server is almost certainly objecting to this weird URL:
GET http://ap1492-dsr/../SetSessionVars.php?RoleId=102&HierarchyId=3
Note the superfluous ../. My copy of Apache returns HTTP 400 Bad Request responses for requests with a leading ../. I notice that the reason LWP is requesting this URL is that it receives an HTTP 302 Found response redirecting to it:
Location: ../SetSessionVars.php?RoleId=102&HierarchyId=3
Did you know that strictly speaking the Location header is supposed to contain an absolute URL, not a relative URI reference? Fixing the server to always provide correct absolute URLs in the Location header should solve the issue.
A workaround could be to set $URI::ABS_REMOTE_LEADING_DOTS to 1, because LWP uses the URI library to resolve relative URI references.
In reply to Re: LWP fails where browser succeeds?
by tobyink
in thread LWP fails where browser succeeds?
by jcabraham
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |