Hello!
On Wed, Dec 14, 2022 at 10:02:04PM -0500, Software Info wrote:
> Hi All,
> I would really appreciate some help with this sticky problem. I am
> using nginx as a reverse proxy. I have version 1.20.1 running on
> FreeBSD 13.1. Today I set up for a new domain. I got a wildcard
> certificate f
You can inspect the certificate at
https://www.ssllabs.com/ssltest/
Maybe you will get lucky and it will help you find out what is wrong.
Original Message
From: softwareinfo...@gmail.com
Sent: December 14, 2022 7:02 PM
To: nginx@nginx.org
Reply-to: nginx@nginx.org
Subject:
Hi All,
I would really appreciate some help with this sticky problem. I am
using nginx as a reverse proxy. I have version 1.20.1 running on
FreeBSD 13.1. Today I set up for a new domain. I got a wildcard
certificate for mydomain.com from GoDaddy. I put the paths in
nginx.conf but when I run nginx -
Hello!
On Wed, Dec 14, 2022 at 03:32:00PM +0530, Vishwas Bm wrote:
> Thanks for the response.
> What happens when content-length provided in request is greater than the
> post body size?
> How does nginx handle this case ?
> Does it fail with 400 ?
>
> Also how is the truncation/padding done in
Thanks for the response.
What happens when content-length provided in request is greater than the
post body size?
How does nginx handle this case ?
Does it fail with 400 ?
Also how is the truncation/padding done in case of lesser or higher content
length ?
Regards,
Vishwas
On Sun, Dec 11, 2022
