Re: [PATCH] Support for external listener

[Sander Temme]

On Mar 20, 2006, at 7:57 AM, Brian Akins wrote:

You can do this today like:

Listen 8001

ServerName www.example.com:80
UseCanonicalPhysicalPort Off

That's right, that would work.

ExternalListenerScheme http|https

perhaps servername shoudl be defined like:

ServerName https://www.example.com:443
UseCanonicalScheme On

ServerName fqdn[:port]
ServerAlias hostname [...]
Protocol some-string (never made it into the docs)
UseCanonicalname on|off|dns
UseCanonicalPhysicalPort on|off



canonical
adjective

(...)





S.

--
[EMAIL PROTECTED]              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

I like this. It's, like, three configuration values for the price of one directive. Perhaps what we're looking for is not more directives, but a cleanup and re-interpretation of the existing ones. We currently have: We must be able to clean this up. I would love to get rid of the word 'canonical'. Says the Oxford Dictionary: 1 according to or ordered by canon law : the canonical rites of the Roman Church. When in fact what I believe we mean by 'canonical' is more like 'as configured in httpd.conf' as opposed to 'as may be supplied by the client Host: header'. We must be able to contract that into some concise CamelCase. I like brian's idea of expanding ServerName to a URL-like construction. That way, we get everything in one place that we may ever want to trick the client into thinking we are, and inform the backend how the client sees us.

smime.p7s
Description: S/MIME cryptographic signature