On 26/12/2017 21:13, Simone Bordet wrote:
Hi,
On Tue, Dec 26, 2017 at 6:06 PM, John English <[email protected]> wrote:
3) Requests to https://www.foo.com go to the primary webapp as expected.
Requests to https://www.bar.com result in an empty 502 response ("Bad
Gateway").
Can anyone suggest what might be going wrong here in case (3)?
I would verify that you don't have a bad /etc/hosts on your local
machine, resolving bar.com to some address you don't expect.
I forgot to mention: I also see the request to bar.com in the request
log, where it's logged as e.g.
185.18.139.12 - - [26/Dec/2017:16:32:32 +0000] "GET / HTTP/1.1" 502 0
so DNS resolution is definitely not the issue. The fact that it's a "bad
gateway" response definitely suggests that the request is getting to the
proxy webapp.
Is there perhaps some way to run the proxy in a debug mode without
having to run the entire system in debug mode? This is a live system
with quite a few users, so I'm likely to get swamped with lots of
irrelevant information.
--
John English
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
