On 2012-07-27 06:05, Phil Pennock wrote:
> On 2012-07-26 at 09:40 -0400, Phil Benchoff wrote:
...
> Hrm, for full compliance with HTTP, we really need:
> proxy_pass_header Server;
>
Thanks for the tip
> Now, doing this breaks the current pool checks, because the Server:
> header goes back t
On 2012-07-26 at 09:40 -0400, Phil Benchoff wrote:
> server {
> listen ...
> root /your/keyserver/web;
> location /pks {
> proxy_pass http://localhost:11371/pks;
> add_header Via "1.1 keyserver.example.com";
> }
> }
>
> I don't have a good setup to fully test this confi
On 07/26/2012 10:40 AM, Kristian Fiskerstrand wrote:
> add_header Via "1.1 keys.kfwebs.net";
I've added a similar directive to the nginx configuration on
zimmermann.mayfirst.org.
--dkg
signature.asc
Description: OpenPGP digital signature
___
On 2012-07-26 15:40, Phil Benchoff wrote:
> Pulling this out of the thread about keyserver.cns.vt.edu:
>
> Nginx can set a Via: header in http responses:
>
> add_header Via "1.1 keyserver.example.com";
>
> http://wiki.nginx.org/HttpHeadersModule#add_header
>
> (Note that it only adds the he
Pulling this out of the thread about keyserver.cns.vt.edu:
Nginx can set a Via: header in http responses:
add_header Via "1.1 keyserver.example.com";
http://wiki.nginx.org/HttpHeadersModule#add_header
(Note that it only adds the header on responses with result codes
200, 204, 301, 302 or 30
