Hello!
On Mon, May 11, 2020 at 09:38:12AM -1000, Bruce Klein wrote:
> Hi Maxim,
>
> Thank you the reply, which I appreciate very much. I fully agree in spirit.
>
> In practice, the issue of previous versions not working on WSL is a
> long-standing bug vs WSL that people far more expert than me
Hello, Maxim, thank you.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,287966,288002#msg-288002
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
I'm trying to set up a reverse proxy with NGNIX on a Ubuntu Server. The
upstream server is IIS configured with basic authentication working only as
https since it has a 301 redirection configured on it.
Here is my conf file
server {
listen 80;
return 301 https://$host$request_uri;
}
server
Hi Maxim,
Thank you the reply, which I appreciate very much. I fully agree in spirit.
In practice, the issue of previous versions not working on WSL is a
long-standing bug vs WSL that people far more expert than me on unix
internals, WSL, nginx, and fpm have not yet solved for two years plus,
oth
Hello!
On Mon, May 11, 2020 at 08:39:22AM -1000, Bruce Klein wrote:
> Does anyone have nginx 1.18.0 running successfully on WSL?
>
> Previous versions have worked fine for me the past couple years as long as
> the standard WSL fix "fastcgi_buffering off" was applied.
>
> I just picked up the 1.
Does anyone have nginx 1.18.0 running successfully on WSL?
Previous versions have worked fine for me the past couple years as long as
the standard WSL fix "fastcgi_buffering off" was applied.
I just picked up the 1.18.0 update and now I'm back to the old
net::ERR_INCOMPLETE_CHUNKED_ENCODING error
Hello!
On Mon, May 11, 2020 at 01:17:28AM -0400, q1548 wrote:
> Thank you, Maxim. If I use the latest nginx version with custom http module,
> for a socket leak, what I need check in module code? thanks.
If you are using a 3rd party module, more or less any bug in the
module can result in a soc
> server {
> location / {
> root
> /home/marco/webMatters/vueMatters/ggc/src/components/auth/weights;
>}
> }
Since it's under /home most likely nginx has no access to the directory.
Check the user under which nginx is running (probably nobody) and try to check
if you can read the fil
Following the indications here:
https://docs.nginx.com/nginx/admin-guide/web-server/serving-static-content/
I modified the lines in /etc/nginx/conf.d/default.conf as follows:
server {
root
/home/marco/webMatters/vueMatters/GraspGlobalChances/src/components/auth/weights;
location / {
I'm trying to figure out how to load static files .
I added to /etc/nginx/conf.d/default.conf the following lines:
server {
location / {
root
/home/marco/webMatters/vueMatters/ggc/src/components/auth/weights;
}
}
But I'm still getting this error: Uncaught (in promise) SyntaxError:
I understand the nginx would proxy the header first and then the body, in
the case the connection with the upstream is broken during the transfer of
body, what status code the client would get? since the nginx would proxy the
200 OK from upstream first to the client, but will nginx send another 5xx
11 matches
Mail list logo
