Pound Mailing List
Expect header support
/ Piyush Devnani <piyush.devnani(at)gmail.com>
The HTTP/1.1 spec allows for clients to send an 'Expect: 100-continue'
header for large request payloads (8.2.3 Use of the 100 (Continue) Status -
Hypertext Transfer Protocol -- HTTP/1.1 - RFC2616).
RE: [Pound Mailing List] Bugfix for RPC
/ Joe Gooch <mrwizard(at)k12system.com>
I've applied this to the stage for upstream 2.7c branch on github.
WebDAV behind Pound?
/ Stephan Fabel <sfabel(at)hawaii.edu>
We're trying to deploy ownCloud (www.owncloud.org) behind a pound reverse
proxy arrangement. We're unwrapping the SSL at pound and load balance based on
Are there any known problems to us...
Bugfix for RPC
/ "Frank Schmirler" <frank.schmirler(at)linogate.com>
the attached patch fixes a problem with the RPC-over-HTTP code not working
with NTLM/Kerberos authentication. A request must only be treated as an RPC if
the content length is between 128kB and 2...
support for passback of responses for expect 100-continue PUT requests
/ "Corrigan, Coleman" <coleman.corrigan(at)hp.com>
With the talk of a 2.7 version of Pound, I was wondering if there are plans to include better handling of PUT requests with expect: 100-continue headers ?
[Pound Mailing List] Disabling SSL Compression option in Stable Release
/ Stefan Eriksson <stefan(at)glesys.se>
> > You can use my stage for 2.7b branch if that's easier, which already has the CRIME patch applied for openssl
pre 1.0 and 1.0+.
Getting 500 errors with large headers
/ Dan Finn <dfinn(at)backcountry.com>
It looks like we are having issues with pound and headers of a certain size. Iím seeing this error in the log:
Nov 10 04:21:40 ip-10-203-87-209 pound: (7fe015975700) e500 can't read header
I can d...
/ Jari Fredriksson <jari.fredriksson(at)digital-identity.com>
We are using Pound on CentOS 6.4 and behind is Liferay 6.0.6. We get
server errors when logging in to the Liferay. Possibly after the Liferay
session was not properly terminated with logoff b...
Re: [Pound Mailing List] Re: NULL: get_thr_arg spamming my syslog
/ Emilio Campos <emilio.campos.martin(at)gmail.com>
Hi, as information to this issue.
I just reproduced this issue with pound 2.6, and 3K Threads for a HTTPS
I applied the patch to 2.6 and my issue is solved, great!, but I just
Re: [Pound Mailing List] Does Pound cache DNS records beyond their TTL?
/ Vebjorn Ljosa <vebjorn(at)ljosa.com>
On Thu, Oct 24, 2013 at 2:58 AM, Leo <neleo(at)gmx.net> wrote:
> the DNS resolution will be done only once at startup. That means IP
> address changes will not be honoured by Pound during runtime
Pound with https:https -- issue with .pem cert in /etc/pound
/ Cory Sanders <cory(at)securecloudsolutions.com>
I have a server running ProxMox (Debian).
Server is running a public IP on eth0.
Here is /etc/network/interfaces:
iface lo inet loopback
iface eth0 inet static
Re: [Pound Mailing List] Pound 2.6 on CentOS 5 2.6.18
/ "Simon Matter" <simon.matter(at)invoca.ch>
> I tried to build Pound 2.6 on a CentOS 5 server and got a "no OpenSSL"
> error during the configure script.
> This machine has Pound 2.5 on it, and I updated the OpenSSL via yum.