Hello,
I just noticed (when accessing squeaksource.com from the Monticello
browser in a trunk image) that this does not work at all.
squeaksource.com replies with a "Location:" header that contains a path
name, but that does not work with HTTPSocket at all.
HTTP 1.1 defines that Location must be an absolute URI, so
squeaksource.com is clearly violating the specs, but browser seem to
handle the Location header just fine.

One side or the other should fix this. I would prefer if squeaksource
would conform to the standard...

Cheers,
Hans-Martin