Hi,
When I send a request with too longer header value to nginx 1.16.1, I get
400 Bad Request response code and default nginx error page.
If I create a custom error page:
error_page 494 /my4xx.html;
now I can see my error page but the http response code becomes 494. Is that
a bug?
Shall I see 400
since i do this through haproxy, it will be a little different, but where
ever port 80 is open to you can have a block that does the following
so in the http block of haproxy i send it to a backend when it meets
these requirements.
acl letsencrypt-request path_beg -i /.well-known/acme-challenge/
r
My first post here as we had never any problems with nginx.
We use 5 nginx server as loadbalancers for our spring boot application.
We were running them for years on debian 9 with the default nginx package
1.10.3
Now we switched three of our loadbalancers to debian 10 with nginx 1.14.2
First ev
Dear NGINX community,
I hope this is the correct channel to ask a question but I have a big probelm
with NGINX.
Currently I am trying to start a streaming service. It is for a school project.
I have multiple streams incoming. But each stream has only one owner which is
allowed to watch it.
What
On Sat, Feb 01, 2020 at 04:45:00AM -0500, MarcoI wrote:
Hi there,
> This is the "view source" of the html page:
This source does not include the words "Welcome to Your Vue.js App",
which appears in "16.jpg" picture.
That picture shows three other successful requests -- app.js,
chunk-vendor.js,
On Fri, Jan 31, 2020 at 10:33:31PM +0100, bagagerek wrote:
Hi there,
> I followed the manual but I can't seem tot get it right. I've forwarded port
> 8081 on my router.
If you want letsencrypt to use the "http" challenge, you must let incoming
traffic in on port 80 (and, presumably, send it to n
