Markus Moeller huaraz at moeller.plus.com writes:
Good news.
Thank you for sharing.
Markus
Can this be fixed in some way?
Because selinux is required by our security policies.
Hi Friends,
How to delete the X- headers in request headers?
Thanks
On 13/08/2012 8:17 p.m., Sekar Duraisamy wrote:
Hi Friends,
How to delete the X- headers in request headers?
Thanks
Squid-3.2 allows reply_header_access to remove/deny custom headers.
Amos
On 9/08/2012 6:16 a.m., Ralf Hildebrandt wrote:
* Amos Jeffries squ...@treenet.co.nz:
This is the counter of how many error responses were generated and
logged by Squid.
OK
Are you using deny_info redirection? (this counter includes the
200/30x responses from that hack)
Yes, massively
On 13/08/2012 10:05 p.m., Sekar Duraisamy wrote:
Hi Friends,
I have tried with
request_header_replace X- none
Iam getting parse_http_header_replace: unknown header name
Can't we remove the headers starts with X- like regex?
Because it is not a regex. It is the full header name.
The
On Thu, Aug 9, 2012 at 9:36 PM, Davide Alberani
davide.alber...@gmail.com wrote:
Maybe we have a bug in FIRSTUP_PARENT selection not checking the
cache_peer_access properly.
I'll do some tests in the next days, and let you know the results.
After a test with squid-3.2.0.19-20120813-r11646, I
You probably need to ask on a SELINUX mailing list. I don't see a reason
why SELINUX behaves different on x64 compared to x86.
Markus
Viorel Robu viorelr...@yahoo.com wrote in message
news:loom.20120813t094910-...@post.gmane.org...
Markus Moeller huaraz at moeller.plus.com writes:
Good
-3.2.0.19-20120813-r11646, I can confirm that
the problem is no longer present for HTTP traffic, thank you very
much!
Now, I have a different issue: HTTP is passed to the upstream proxy,
but - after I've enabled ssl-bump - HTTPS is not (it's handled
directly
by squid itself).
Is this expected?
Yes