jean-frederic clere <[EMAIL PROTECTED]> wrote:
> Ryan Bloom wrote:
>>
>> Hi.
>>
>> The big thing about ServerName in 2.0 is that it has taken over for the Port
>> directive from 1.3. So, the following config means that the server
>> listens on 127.0.0.1, port 8080, but reports itself as foo.com on port 80.
>>
>> <VirtualHost 127.0.0.1:8080>
>> ServerName foo.com:80
>> </VirtualHost>
>>
>> That reporting is done whenever the server creates a self-referential
>> URL, which is done by mod_dir, and in all error pages among other
>> places in the code.
>>
>> The ServerName directive NEVER controls the port that the server
>> actuall listens on.
>
> Hi,
>
> That brings a small problem in mod_webapp:
> The ServerName hostname:port is used to build the virtual host for Tomcat.
> A redirect from Tomcat will come for hostname:port...
> This fails if the port is not the one used for the listen...
>
> Any hints to solve this?
This whole thing is _screwed_ in Tomcat... I posted a couple of months ago
about it on the list, but apparently noone wants to fix it (or "it fucked
but it works for them")... Bah... I'm tired...
Pier
