Article

HTTPClient - Location header is appended instead of being added as a path

Information

 
Article Number000093507
EnvironmentProduct: OpenEdge
Version: 11.7.x
Other: httpclient
Question/Problem Description
Application uses httpclient to make a request to a 3rd party webservice. 
If the user is not authenticated, the webservice redirects the user to the login page.

Example of Header HTTP response:
HTTP/1.1 302 Found
Server: nginx
Date: <date-time>
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Set-Cookie: PHPSESSID=i0srttafkehhvegvdh8ej1sgd2; path=/
Expires: <date-time>
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Location: login
Strict-Transport-Security: max-age=16000000; includeSubDomains; preload;
Set-Cookie: PROSRVID=www3; path=/

Causing the error : 
Secure Socket Layer (SSL) failure. error code 11001: Unknown
network error (9318)
Unknown hostname mycustomdomain.comlogin. (5482)
Steps to Reproduce
Clarifying Information
All the certificates were correctly imported to OpenEdge certs store.
Error MessageSecure Socket Layer (SSL) failure. error code 11001: Unknown network error (9318)
Unknown hostname <domain><location-header>. (5482)
Defect/Enhancement NumberDefect ADAS-12764
Cause
The HTTP spec allows for the Location header to have a relative URI (see https://tools.ietf.org/html/rfc7231#section-7.1.2 ), which the HTTP client does not handle properly.
Resolution
The fix for this issue is expected to be in the upcoming release 11.7.5. As of 12/21/2018, release 11.7.5 is scheduled to be released in Q2/2019, although dates and content of the release are subject to change.
Workaround
Notes
Attachment 
Last Modified Date12/21/2018 7:30 PM


Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025