Alain,
I'm trying to help, and I'm sorry that you feel that I'm snubbing users.
I'm happy to take feedback on what I should be doing instead. Please can
you explain how you think I've snubbed users here?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Same problem here.
Works fine with 1.9.0+svn250-3
Broken with 1.9.0+svn250-5 (Package for vivid, installed on a trusty)
Btw, Robie, if you snub one user, in reality you also snub hundreds of others
who find his bug report by googling for the same symptoms, so please be a bit
more helpful. It
Found it.
Actually it was due to both a pecularity in the proxy server I wanted to
get through, and a bug in how proxytunnel sets SNI.
It seems that our proxy server ignores SNI in SSLv3, but considers it in
TLSv1.
And proxytunnel sets the wrong SNI.
proxytunnel ---> proxy1 (the one I want to
Same problem here
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1158141
Title:
apache2 forward proxy socket read error
To manage notifications about this bug go to:
Tim,
Sorry but this is a bug tracker, not a support forum. Please continue
trying the forums, or the ubuntu-server mailing list, askubuntu.com or
IRC.
** Changed in: apache2 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, so I'm marking this bug as Incomplete.
If this is indeed a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community
I have requested help already via the forums, but didn't get an answer.
I guess it's an Apache problem because the error is a socket read error, but I
don't know enough to test this. I actually don't know what a socket read error
means. There one another reports of similar problems on RedHat,
