peter at digitalbrains.com
Sun Nov 6 13:55:32 CET 2016
On 06/11/16 13:40, Jürgen Schäpker wrote:
> My question was apparently ambiguous. My concern is the WKD server. How
> does a WKD server know which domain it is serving for when the request
> HOST header is modified (e.g. by a reverse proxy) and so the domain-part
> cannot be determined from that.
This doesn't seem to be a concern of this (draft) standard. HTTP Host: is well
standardized and defined. You should solve this there, in your webserver/proxy.
This is just sensible layering of protocols. You should strive to solve the
problems in the correct layer. Sometimes a little layering violation is still
the lesser of evils, but I really don't think that applies here. *Especially*
with IDN! That only makes it worse. How many independent IDN implementations in
how many layers do you want to add?
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>
More information about the Gnupg-devel