[Seaside] seaside.st seems to be down.

[Adrian Lienhard]

On Jul 26, 2009, at 00:13 , Julian Fitzell wrote:

[...]

> The infinite redirection is caused by an unusual (but according to the
> HTTP spec valid) implementation choice in HTTPSocket that seems to
> confuse web servers (one that I've run into before... see
> http://tiny.cc/suckygooglesupport for how Google won't fix their
> servers). HTTPSocket always includes the port in the Host: header when
> making an HTTP request, even when it is the default port. In Google's
> case, the server obviously fails to normalize the URL and realize that
> port 80 is the default port and is therefore the same as the URL
> without the port. In the case of this blog feed, the server also fails
> to normalize. It correctly redirects
>
> http://old.feed.address/ to: http://new.feed.address/
>
> but incorrectly redirects
>
> http://old.feed.address:80/ to http://old.feed.address/
>
> Since HTTPSocket submits the latter address back as
> http://old.feed.address:80/ you can see how we carry on ad infinitum.
>
> Diagnosis:
> 1) Obviously HTTPSocket should catch the infinite redirection.
> 2) Pier's blog component also probably shouldn't be allowing a slow
> blog feed update to prevent answering requests for the site.
> 3) Maybe someone should also change HTTPSocket to normalize URLs
> before submitting... it seems to be causing recurring problems
> 4) Maybe we should install the CURL plugin on seaside.st?

A month ago I looked at the very same problem for a bug reported in  
Pharo:

http://code.google.com/p/pharo/issues/detail?id=907

Since this does not seem to be an isolated problem, I think we should  
normalize URLs to work around the problem in the short run.

Adrian