Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36157 - [subversion][PATCH] Fix reverse proxy issues in 1.8.0.

Attached to Project: Arch Linux
Opened by Raphael Kubo da Costa (rakuco) - Monday, 15 July 2013, 10:36 GMT
Last edited by Angel Velasquez (angvp) - Thursday, 01 August 2013, 23:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Angel Velasquez (angvp)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Subversion 1.8.0 has a bug that prevents people behind proxies (at $WORK, for example) from checking out or updating http/https repositories.

The attached patch includes an upstream commit to fix the issue. It will be part of 1.8.1.

I've created the patch against packages/subversion/trunk instead of packages/subversion/repos, please let me know if that's not right.
This task depends upon

Closed by  Angel Velasquez (angvp)
Thursday, 01 August 2013, 23:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1.8.1
Comment by Michaël Bruneel (mbruneel) - Wednesday, 17 July 2013, 18:38 GMT
We get this error message: svn: E175009: XML parsing failed: (400 Bad Request)
Comment by Raphael Kubo da Costa (rakuco) - Thursday, 18 July 2013, 12:02 GMT
In my case, I didn't get any error -- svn checkout or svn update would simply not checkout or update anything at all, so I'd end up with an empty directory.

If the patch also solves your problem, that's even better :-)
Comment by Michaël Bruneel (mbruneel) - Wednesday, 31 July 2013, 18:18 GMT
See http://subversion.apache.org/docs/release-notes/1.8.html#issues

"Subversion 1.8.0 has switched from neon to serf for HTTP access. The Serf-based HTTP access library would use chunked transfer encoding for most requests. When the mod_dav_svn Subversion server is fronted by a proxy or reverse proxy (such as Nginx prior to 1.3.9) which responds with a 411 Length Required, Subversion would sometimes either treat this as a fatal error, such as [...] svn: E175009: XML parsing failed: (411 Length Required) [...] Subversion 1.8.1 fixes this issue by detecting automatically whether chunked requests are supported at the set up of a session. This is done by issuing one additional request at the start of the session."
Comment by Michaël Bruneel (mbruneel) - Wednesday, 31 July 2013, 18:19 GMT
Thank you Raphael for the patch :-)

Loading...