[Seaside] Seaside and absolute URLs

[Todd Blanchard]

Yeah, I'm gonna keep hacking that out then.

First - there's no apache when I'm developing.
Second - not a lot of hosting providers have approved apache 2 (like  
mine).
Third - moving an image to a new box where the hostname has been set  
prevents access to the web tools to change the host name.

I don't mind if it is syntactically wrong if it works right.  I don't  
much like it if it is syntactically right but doesn't work at all.

On Oct 10, 2007, at 9:17 AM, Lukas Renggli wrote:

>> I don't get why seaside insists on generating absolute urls at all.
>> It seems to be bad practice.
>
> HTTP redirects are required to be absolute. Most browser can handle
> relative redirects, but it is syntactically wrong.
>
>> Consider one apache doing load
>> balancing to multiple application servers.  Seems more flexible to
>> use relative urls (and, in fact, this is the first hack I make to any
>> seaside - I kill off the absolute url code).
>
> That's not a issue, because Seaside can automatically detect the
> currently used host-name using Apache 2.
>
> Cheers,
> Lukas
>
> -- 
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside