Hello!
On Thu, Nov 22, 2018 at 09:11:59PM +0100, Jack Henschel wrote:
> Hello everyone,
>
> during my last debugging session with Nginx I was wondering how and when
> exactly Nginx passes upstream's hostname when proxying a request.
>
> In particular, I have the following example:
> > upstream
Hello everyone,
during my last debugging session with Nginx I was wondering how and when
exactly Nginx passes upstream's hostname when proxying a request.
In particular, I have the following example:
> upstream backend {
> server a.example.com:443;
> server b.example.com:443;
> }
> server {
On Sunday, 18 November 2018 18:06:27 MSK Antoine Bonavita wrote:
> Hello Valentin,
>
> And thank you for your prompt answer. Writing such a http client and making
> it available is probably a pretty big work. But if I were to write a
> "limited" one that would fit my simple needs (GET only, only H
Hello!
On Thu, Nov 22, 2018 at 07:15:41AM -0500, Ortal wrote:
> This is a small example of my code, I changed the code and in the current
> version on post/put request trying to read the buffer and print it, on any
> other requests just send response (I tried to minimal it as much as I
> could)
>
This is a small example of my code, I changed the code and in the current
version on post/put request trying to read the buffer and print it, on any
other requests just send response (I tried to minimal it as much as I
could)
On the current flow when running a post request with 1MB data the
ngx_ht
Hello,
after i switch my error log to info level (to find an other Problem) I
get a lot of messages like:
"client sent plain HTTP request to HTTPS port while reading client
request headers"
I search for a solution and always found that this error is shown when
http and https is in one server {}
