Re: Nginx 1.17.0 doesn't change the content-type header

Hello, I missed the cache status header in my previous email. This is another response with all the headers: https://example.com/hls/5d0f9398852b84.49917460/1280_720_1300_5d0f9398852b84.49917460_4.ts

how to force/send TLS Certificate Request for all client connections, in client-side ssl-verification?

I've setup my nginx server with self-signed SSL server-side certs, using my own/local CA. Without client-side verifications, i.e. just an unverified-TLS connection, all's good. If I enable client-side SSL cert verification with, ssl_certificate "ssl/example.com.server.crt.pem

Re: effect of bcrypt hash $cost on HTTP Basic authentication's login performance?

Hello! On Tue, Jul 02, 2019 at 05:55:01PM -0700, PGNet Dev wrote: > On 7/2/19 5:23 PM, Maxim Dounin wrote: > > On Sat, Jun 29, 2019 at 09:48:01AM -0700, PGNet Dev wrote: > > > >> When generating hashed data for "HTTP Basic" login auth > >> protection, using bcrypt as the hash algorithm, one can

Re: request authorization with grpc (failure status code)

Hello! On Tue, Jul 02, 2019 at 11:19:54AM -0400, bmacphee wrote: > I have an nginx configuration that passes gRPC API requests to other > services an authorization endpoint that is used in conjunction. > > This works great when authorization is successful (my HTTP1 authorization > endpoint retur

Re: effect of bcrypt hash $cost on HTTP Basic authentication's login performance?

> (And no, it does not look like an appropriate question for the > nginx-devel@ list. Consider using nginx@ instead.) k. On 7/2/19 5:23 PM, Maxim Dounin wrote: On Sat, Jun 29, 2019 at 09:48:01AM -0700, PGNet Dev wrote: When generating hashed data for "HTTP Basic" login auth protection, usin

Re: Nginx 1.17.0 doesn't change the content-type header

Hello! On Sat, Jun 29, 2019 at 10:49:00PM +, Andrew Andonopoulos wrote: > I have the following config in the http: > > include mime.types; > default_type application/octet-stream; > > > also i have this in the location: > > types { > application/vnd.apple.mpegurl m3u8

request authorization with grpc (failure status code)

I have an nginx configuration that passes gRPC API requests to other services an authorization endpoint that is used in conjunction. This works great when authorization is successful (my HTTP1 authorization endpoint returns HTTP 2xx status codes). When authorization fails (it returns 401), the gR

Re: auth_request with grpc

I was about to ask a related question. Here is a sample of my config. The only issue is that the gRPC client gets a StatusCode.Cancelled when authorization fails. In this scenario, the auth service at http://auth:5000 is a simple flask application performing the auth with a 3rd party identity pr

RE: set_real_ip_from behavior

> I'm having some issues with getting X-Forwarded-For set consistently for > upstream proxy requests. The server runs Nginx/OpenResty in front of > Apache, and has domains hosted behind Cloudflare as well as direct. The ones > behind Cloudflare show the correct X-Forwarded-For header being > set

set_real_ip_from behavior

Hello, I'm having some issues with getting X-Forwarded-For set consistently for upstream proxy requests. The server runs Nginx/OpenResty in front of Apache, and has domains hosted behind Cloudflare as well as direct. The ones behind Cloudflare show the correct X-Forwarded-For header being set, usi