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

Squid reverse proxy switching peers fix. Issue 10450 #839

Merged
merged 1 commit into from
Apr 14, 2020

Conversation

vktg
Copy link
Contributor

@vktg vktg commented Apr 13, 2020

Redmine Issue: https://redmine.pfsense.org/issues/10450
Ready for review

https://forum.netgate.com/topic/118255/squid-reverse-proxy-switching-peers:

I want Squid to direct incoming requests to a specific peer based on URI, but what I'm getting instead is it's sending the requests to each peer in a round-robin fashion. So, once in a while, I get the content, or sometimes I get a 404 when it's hitting the wrong peer. I only have one peer selected per mapping.
...
I have a working solution that might have to be re-implemented if and when I update the squid package. The trick is to add cache_peer_access directives that specifically deny the peers from the other mappings. For some reason, the "deny allsrc" that is automatically generated is not cutting it.

@vktg
Copy link
Contributor Author

vktg commented Apr 13, 2020

it also adds extra input validation for Squid reverse proxy pages
to avoid 'Squid Reverse Proxy alternating between destinations' bug:
https://redmine.pfsense.org/issues/7797
caused by space symbols in Peer Alias

@netgate-git-updates netgate-git-updates merged commit def3ce0 into pfsense:devel Apr 14, 2020
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

Successfully merging this pull request may close these issues.

3 participants