Tom Schindl wrote:
I would expect none of these solutions to work:
Don;t know if you read my reply to that with the handler example.
1. Solution:
- ------------
Where from should perl know which port you are refering to / interested
in or turn it the other way round what happens when you server listens
to more than one port on more than one IP addresses?
- ---------------8<-----------------
Listen 192.170.2.1:80
Listen 192.170.2.5:8000
- ---------------8<-----------------
This is a good point.
I haven't read the HTTP-API docs of this function but in short this API
doesn't make any sense at least it should return a List and not a Scalar.
I believe the API is copied from httpd's ap [ap_get_server_port()] via XS glue.
2. Solution:
- ------------
Where from should perl have a request in the startup-phase? The API in
request-context makes sense because an request is really made to one port.
Agreed. Which is why my _1st_ response made no sense in hind sight.
You want is retrieving configuration values which can be done using
Apache2::Directive:
I had thought about that, I knew it would work, but I discounted from some
reason -- can't remember why though.
--
END
------------------------------------------------------------
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci ([EMAIL PROTECTED]) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
