|Summary:||net-libs/serf doesn't support HTTP/1.0 proxies|
|Product:||Gentoo Linux||Reporter:||Robin Johnson <robbat2>|
|Component:||Current packages||Assignee:||Arfrever Frehtes Taifersar Arahesis <arfrever.fta>|
|Severity:||normal||CC:||dberkholz, devurandom, jstein, kunitoki, marcuzero, msulli1355|
|Package list:||Runtime testing required:||---|
Description Robin Johnson 2008-10-11 07:08:05 UTC
I've placed this issue up at critical, because fox2mike discovered it while we were working on the svn.overlays migration onto the new server. When we do the switchover, it's going to break everybody that is using serf instead of neon. How to reproduce: 1. Set up Apache with SVN 2. Put squid in front of Apache 3. USE="webdav-serf -webdav-neon" emerge subversion 4. # svn co http://overlaystest.gentoo.org/svn/proj/php/ Actual results: svn: XML parsing failed: (411 Length Required) Doing a tcpdump on during the co request, and comparing the requests, the Neon version sends PROPFIND with Content-Length, while serf sends PROPFIND without Content-Length, which thus upsets squid.
Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2008-10-11 22:56:48 UTC
(In reply to comment #0) > 3. USE="webdav-serf -webdav-neon" emerge subversion FYI, if you have Subversion installed with USE="webdav-neon webdav-serf", then you can enforce the use of Serf by setting the 'http-library' option in ~/.subversion/servers: [global] http-library = serf
Comment 2 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2008-10-20 12:14:32 UTC
Comment 3 Elias Probst 2008-10-23 17:44:49 UTC
I'd vote for masking the webdav-serf USE flag for now as the serf support causes currently way too much problems.
Comment 4 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2008-10-24 18:31:49 UTC
(In reply to comment #3) > I'd vote for masking the webdav-serf USE flag for now -1 for masking this flag. An elog notice in the ebuild will be sufficient.
Comment 5 Mark Zhitomirski 2008-11-23 14:03:04 UTC
> An elog notice in the ebuild will be sufficient. > I've came to an issue with subversion + USE="webdav-serf" while simply checking out Django svn co http://code.djangoproject.com/svn/django/trunk Moreover svn co https://<same addr> segfaults.
Comment 6 Doug Goldstein 2008-12-15 19:52:26 UTC
*** Bug 250447 has been marked as a duplicate of this bug. ***
Comment 7 Dennis Schridde 2009-01-18 01:00:59 UTC
Any updates on this recently?
Comment 8 Casper Star 2009-03-10 14:34:56 UTC
(In reply to comment #5) > > An elog notice in the ebuild will be sufficient. > > > I've came to an issue with subversion + USE="webdav-serf" while simply checking > out Django > svn co http://code.djangoproject.com/svn/django/trunk > > Moreover svn co https://<same addr> segfaults. > Same here. Problem still exists.
Comment 9 kunitoki (Lucio Asnaghi) 2009-05-13 16:30:24 UTC
same problem here, subversion is quite unusable on this machine getting a lot of svn: OPTIONS of 'http://svn.repository.site': could not connect to server (http://svn.repository.site) please help !!!
Comment 10 Robin Johnson 2009-05-13 19:02:09 UTC
kunitoki: just rebuild with USE=-webdav-serf P.S. If you ask a question, add yourself to the CC list!
Comment 11 kunitoki (Lucio Asnaghi) 2009-05-13 22:34:18 UTC
ok now is going better (using only neon), but i'm still having issues with using >=neon-0.28.4: that neon version should be had masked at least ! Look here: http://bugs.gentoo.org/show_bug.cgi?id=264101 Ok i finally got subversion working again. I please the great gentoo developers to check at least some critical apps (like subversion is for other DEVELOPERS) before committing stable keywords to them.
Comment 12 Markos Chandras (RETIRED) 2012-03-24 09:43:28 UTC
Is this bug still valid?
Comment 13 Dennis Schridde 2012-03-24 10:09:05 UTC
(In reply to comment #12) > Is this bug still valid? Upstream bug  is still open.  http://code.google.com/p/serf/issues/detail?id=28
Comment 14 Sven Vermeulen (RETIRED) 2013-12-31 21:11:24 UTC
It doesn't look like upstream is going to fix this soon. Can we at least add in a notification about the issue through elog/ewarn?
Comment 15 Arfrever Frehtes Taifersar Arahesis 2013-12-31 22:25:46 UTC
Comment #5 in Serf issue #28 suggests that Subversion now (since 2012) contains a workaround for this bug in Serf. Could somebody test if this problem still occurs with newest Subversion?
Comment 16 Arfrever Frehtes Taifersar Arahesis 2013-12-31 22:29:39 UTC
It seems that the fix is only in Subversion 1.8.*.
Comment 17 Jonas Stein 2017-07-21 21:41:07 UTC
any news? upstream is now at serf-1.3.9