Welcome! Log In Create A New Profile

Advanced

Doing an "upstream" request without sending result back to client

Vincent Gross
December 02, 2013 05:24AM
Hi folks,

I want to implemement a webid authn module in nginx. This is the big picture:

1. Client do an https request and sends a client cert
2. Certs contains a subjectAltName URI, e.g. https://mysite.info/id/
3. Server fetches https://mysite.info/id/ content
4. If content do contains public key info matching client cert, authn
successful.

From what I see in src/http/ngx_http_upstream.c in functions
ngx_http_upstream_process_header(ngx_http_request_t *, ngx_http_upstream_t *)
& ngx_http_upstream_send_response(ngx_http_request_t *, ngx_http_upstream_t *),
it is not possible to do the request [3] without sending back at least a
response header back to the client.

Did I miss something or am I really setting myself for reimplementing the
mechanisms of ngx_http_upstream.c? Any advices/guidelines for the latter (other
then taking example on original upstream?)

Cheers,

--
Vincent
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

Doing an "upstream" request without sending result back to client

Vincent Gross 707 December 02, 2013 05:24AM

Re: Doing an "upstream" request without sending result back to client

Maxim Dounin 302 December 02, 2013 08:50AM

Re: Doing an "upstream" request without sending result back to client

Vincent Gross 342 December 02, 2013 08:28PM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 152
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready