subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <pierre.vi...@postfinance.ch>
Subject AW: AW: AW: AW: AW: Segmentation Fault with SVN Client related to serf
Date Fri, 09 Jan 2015 10:08:03 GMT


> -----Ursprüngliche Nachricht-----
> Von: Philip Martin [mailto:philip.martin@wandisco.com]
> Gesendet: Freitag, 9. Januar 2015 10:48
> An: Viret Pierre, PF54
> Cc: users@subversion.apache.org
> Betreff: Re: AW: AW: AW: AW: Segmentation Fault with SVN Client related to serf
> 
[...]
> 
> I see why the client switches to the v1 protocol.  Your proxy is changing the case
> of the HTTP headers and "SVN-Me-Resource" becomes "Svn-me-resource".  That
> has uncovered a bug in the client: it does a case-sensitive check for "SVN" before
> doing a case-insensitive check for "svn-me-resource".
> 

Yes you are right, I have not looked at the wireshark output good enough!
Unfortunately I cannot change it in our HttpProxy: this change of the case of the header keys
is performed by the underlying HTTP Layer in java and not by our own code. I think the reason
for this is that the HTTP specification states that the header-keys are case-insensitive (see
f.i. http://stackoverflow.com/questions/5258977/are-http-headers-case-sensitive).
Maybe if this bug is fixed in the svn client then the segmentation fault would be solved?
There might be another header field which is not managed correctly because of case-sensitiveness?

Remarque concernant la sécurité:
Ce courriel provenant de PostFinance est signé. Vous trouverez d'autres informations à ce
sujet sous: 
https://www.postfinance.ch/e-signature.
Ne divulguez jamais vos éléments de sécurité à des tiers.
Mime
View raw message