Re: [users@httpd] reverse proxy issue

In this case, running apachectl -S or httpd -S helps to spot overlaps. Secondly, define all vhosts as *:PORT (only use IP:PORT when you know what you are doing, and NEVER use :PORT). If you're still stuck, share the sanitized version of httpd -S Also, is there a reason why you're still using pre

Re: [users@httpd] reverse proxy issue

Thank you, i think i'm getting the idea Indeed, there are a number of VirtualHost entries and somehow i didn't check if they all fail with described symptoms or just specific one. Therefore my assumption is - when it happens - no matter for what reason - this VirtualHost somehow gets removed from

Re: [users@httpd] reverse proxy issue

How does Apache access the application server? Is the ip address of application server changing (and it coincides with the 404 error)? Deepak "The greatness of a nation can be judged by the way its animals are treated - Mahatma Gandhi" +91 73500 12833 deic...@gmail.com Facebook: https://www.fac

Re: [users@httpd] reverse proxy issue

On Wed, Jun 8, 2022 at 3:21 PM Serge Krawczenko wrote: > > We have application server behind httpd as a reverse proxy, > with basic ldap auth, so only ldap authenticated users are able to get into > the application. > (Require valid-user > Allow from all > ) It's usually not a good idea

[users@httpd] reverse proxy issue

Hello, My issue is very simple but complicated by sudden behavior. We're unable to resolve it for years so decided to request community's help. We have application server behind httpd as a reverse proxy, with basic ldap auth, so only ldap authenticated users are able to get into the application.

Re: [users@httpd] Reverse proxy issue with Chrome

No, there is no further information: GET https://webserver1.com/ 502 (Proxy Error) favicon.ico:1 GET https://webserver1.com/favicon.ico 502 (Proxy Error) Andreas On 14.05.2021 17:00, Michael Wechner wrote: Does your Chrome console have some additional hints? Thanks Michael Am Fr., 14. Mai

Re: [users@httpd] Reverse proxy issue with Chrome

Does your Chrome console have some additional hints? Thanks Michael Am Fr., 14. Mai 2021 um 14:44 Uhr schrieb Andreas Habel < aha...@uni-bremen.de>: > Hello, > > since Chrome and Chrome-based browsers recently were updated to Chrome > 90 I am experiencing a 502 proxy error when I try to access

[users@httpd] Reverse proxy issue with Chrome

Hello, since Chrome and Chrome-based browsers recently were updated to Chrome 90 I am experiencing a 502 proxy error when I try to access my web servers with these browsers. Before the update to Chrome 90 things worked fine, and everything still works with Firefox. Here's my setup:        

Re: [users@httpd] Reverse Proxy Issue on Apache version 2.0.65

On 10 Jan 2014, at 15:43, Otis Dewitt - NOAA Affiliate wrote: > Greetings, > > I am constantly getting this error below in my log file: It's not clear whether your posting this twice was deliberate? Your problem may be that noone on this list feels motivated to revisit the 2.0.x branch to figu

[users@httpd] Reverse Proxy Issue on Apache version 2.0.65

Greetings, I am constantly getting this error below in my log file: *[error] (20014)Error string not specified yet: proxy: pass request body failed to 172.16.11.212:7705 (www.example.com ) from 192.168.100.34 ()* [Thu Jan 09 15:52:47 2014] [err

[users@httpd] Reverse Proxy Issue on Apache version 2.0.65

Greetings, I am constantly getting this error below in my log file: *[error] (20014)Error string not specified yet: proxy: pass request body failed to 172.16.11.212:7705 (www.example.com ) from 192.168.100.34 ()* [Thu Jan 09 15:52:47 2014] [err