httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kasper Laudrup <laud...@linuxfan.dk>
Subject Re: How to get a module to bind on a different port
Date Tue, 14 Nov 2006 22:33:45 GMT
Hi,

That was excactly what I was looking for, thanks a lot!

Regards,
Kasper

Sascha Kersken wrote:
> Hi,
>
> the Listen directive is always part of the Server configuration and
> not a module's business.
> The correct way is to use more than one Listen directive and have a
> virtual host deal with your module stuff.
> For example:
> Listen 80
> Listen YOURPORT
> <VirtualHost *:YOURPORT>
>  YourModuleDirective
> </VirtualHost>
> Look at the documentation on modules like mod_ssl for details (or e.g.
> my own module mod_daytime:
> http://buecher.lingoworld.de/apache2/mod_daytime_en.html)
>
> Hope that helps.
>
> Regards
> Sascha
>
> ----- Original Message ----- From: "Kasper Laudrup" <laudrup@linuxfan.dk>
> To: <dev@httpd.apache.org>
> Sent: Saturday, November 11, 2006 9:45 PM
> Subject: How to get a module to bind on a different port
>
>
>> I'm trying to write a module that listens on another port than port 80,
>> but I have a hard time figuring out how to do that, let alone if it's
>> possible at all. I can change the Listen configuration in Apaches config
>> file, and apache seems to handle request on that port as it would
>> request on any other port, but I'm just wondering if there's a simple
>> way or more "correct" way of doing that apart from getting the port
>> number from the request handle in every connection.
>>
>> Hope someone has any ideas,
>> Thanks a lot,
>> Kasper Laudrup
>>
>> -- 
>> This email has not been scanned for virus. Read at your own risk!
>>
>
>


-- 
This email has not been scanned for virus. Read at your own risk!


Mime
View raw message