By the looks of things, if the application is redirecting to /wfc that's not working, your application doesn't seem to accept that as a valid. The Squid cache is returning a miss and so it is hitting the backend and getting a 404 from there it seems. /wfc/ with a trailing slash does work however, so this looks like an issue with the IIS configuration to me. Also, this is a login form, I'd recommend that you get TLS set up on this (Let's Encrypt's certbot is free afterall).
On Tue, 2020-01-28 at 14:11 +0000, Richard Paul wrote: It doesn't actually redirect to /wfc/ though, or rather your log lines show a 404 at /wfc Also, your log line says /wfc/logon not /wfc/htmlnavigator/logon GET /wfc GET /wfc/logon GET /wfcstatic/applications/wpk/html/scripts/cookie.js?version=8.1.6.2032 On Tue, 2020-01-28 at 14:03 +0000, Johan Gabriel Medina Capois wrote: Sure. The problem is that we have an backend application running in HTML5, when we navigate to <http://kronos.mardom.com/wfc/htmlnavigator/logon> http://kronos.mardom.com/wfc/htmlnavigator/logon and try to login, it redirect to <http://kronos.mardom.com/wfc/> http://kronos.mardom.com/wfc/ and deploy error message "you have no access" , but when navigate from localhost no problem. And the nginx log "GET /wfc HTTP/1.1" 404 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0" "GET /wfc/logon HTTP/1.1" 200 7496 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0" "GET /wfcstatic/applications/wpk/html/scripts/cookie.js?version=8.1.6.2032 HTTP/1.1" 200 2534 " <http://kronos.mardom.com/wfc/logon> http://kronos.mardom.com/wfc/logon " "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0" Configuration is server { listen 80; server_name kronos.mardom.com; location / { proxy_pass <http://10.228.20.97> http://10.228.20.97 ; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } Regards -----Original Message----- From: nginx < <mailto:nginx-boun...@nginx.org> nginx-boun...@nginx.org > On Behalf Of J.R. Sent: Tuesday, January 28, 2020 9:34 AM To: <mailto:nginx@nginx.org> nginx@nginx.org Subject: Re: Help please Can you help us please? You're going to have to be a *bit* more specific what your problem is... _______________________________________________ nginx mailing list <mailto:nginx@nginx.org> nginx@nginx.org <http://mailman.nginx.org/mailman/listinfo/nginx> http://mailman.nginx.org/mailman/listinfo/nginx Johan Medina Administrador de Sistemas e Infraestructura [Logo] Departamento: TECNOLOGIA Central Tel: 809-539-600 Ext: 8139 Flota: (809) 974-4954 Directo: 809 974-4954 Email: <mailto:jmed...@mardom.com> jmed...@mardom.com Web:www.mardom.com<https:://www.mardom.com> [Facebook icon] < <https://www.facebook.com/maritimadelcaribe> https://www.facebook.com/maritimadelcaribe > [Instagram icon] < <https://www.instagram.com/maritimadelcaribe> https://www.instagram.com/maritimadelcaribe > [Linkedin icon] < <https://www.linkedin.com/company/maritima-dominicana-sas/?viewAsMember=true> https://www.linkedin.com/company/maritima-dominicana-sas/?viewAsMember=true > [Youtube icon] [Banner] Sea amable con el medio ambiente: no imprima este correo a menos que sea completamente necesario. _______________________________________________ nginx mailing list <mailto:nginx@nginx.org> nginx@nginx.org <http://mailman.nginx.org/mailman/listinfo/nginx> http://mailman.nginx.org/mailman/listinfo/nginx _______________________________________________ nginx mailing list <mailto:nginx@nginx.org> nginx@nginx.org <http://mailman.nginx.org/mailman/listinfo/nginx> http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
