Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If idleConnectionTimeout is exceeded no response is returned #96

Closed
robfletcher opened this issue Oct 1, 2013 · 3 comments
Closed

If idleConnectionTimeout is exceeded no response is returned #96

robfletcher opened this issue Oct 1, 2013 · 3 comments
Milestone

Comments

@robfletcher
Copy link

I would expect to get a 504 but instead the connection is just terminating. Is there another way to specify the time the proxy should wait for a response from the target server?

@oxtoacart
Copy link
Collaborator

@robfletcher Good catch.

As for setting the timeout - I believe that the option you want is HttpProxyServerBootstrap.withIdleConnectionTimeout()

@robfletcher
Copy link
Author

That's what I'm using. Just wanted to check it's the right thing.

@oxtoacart
Copy link
Collaborator

Yep. I think as part of fixing the missing 504 I might break this into two settings, one for inbound and one for outbound connections.

oxtoacart added a commit that referenced this issue Oct 14, 2013
MediumOne pushed a commit to MediumOne/LittleProxy that referenced this issue Jun 7, 2022
…logging.log4j-log4j-core-2.17.1

Bump log4j-core from 2.17.0 to 2.17.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants