EldoS | Feel safer!

Software components for data protection, secure storage and transfer

HTTPS redirection (302/1) not working with path

Posted: 07/21/2006 04:43:09
by Stephane Grobety (Priority Standard support level)
Joined: 04/18/2006
Posts: 174


It seems that the TElHTTPSClient component does not properly handle HTTP redirection response properly when the "Location" field is set to a path insteand of a URI.

Working exemple: https://mail.fulgan.com/

This site responds in the following way:

302 Moved Temporarily
Server: IceWarp/8.3
Date: Fri, 21 Jul 2006 11:52:26 +0200
Location: /mail/
Content-type: text/html

As you can see, the "location" header points to an absolute path on the same server. Unfortunately, the component doesn't seem to recognize that sytax and tries to connect to a "/mail" URL and failts to resolve it.
Posted: 07/21/2006 13:05:43
by Eugene Mayevski (Team)

Right, cause such relocation path doesn't conform to HTTP afair. Of course, we will add a workaround, but this is not standard-compliant.

Sincerely yours
Eugene Mayevski
Posted: 07/22/2006 02:51:26
by Eugene Mayevski (Team)


The Location response-header field is used to redirect the recipient
to a location other than the Request-URI for completion of the
request or identification of a new resource. For 201 (Created)
responses, the Location is that of the new resource which was created
by the request. For 3xx responses, the location SHOULD indicate the
server's preferred URI for automatic redirection to the resource. The
field value consists of a single absolute URI.

Location = "Location" ":" absoluteURI

Sincerely yours
Eugene Mayevski
Posted: 07/22/2006 03:11:10
by Eugene Mayevski (Team)

Nevermind, I've already implemented the workaround.

Sincerely yours
Eugene Mayevski



Topic viewed 4123 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!