Is it valid for an HHTP header to relocate to an empty URL?

Currently, HttpProt seems to parse the relocation to the same URL, and
goes into a loop.

< HTTP/1.1 302 Found
< Location: http://

Probably the loop is broken by the server side once you handle cookies. The first request produce a relocation which is accompanied by a cookie. Then the relocation reload the same page as no URL is given. But this time the server application "see" the cookie and produce another result which is not a relocation to the same page.

So the loop only occur if you do not handle the cookies correctly.

Since you rae writing a page check software, it is probably ggod enough to not handle the cookies and to refuse relocation if the url is the same url. You know that the page is still active and no need to go further.

The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)

To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to