[PATCH] fix for unparsable DAV:href values

[Tobias Krause]

Hi Joe,

I'd like to vote for this patch to get it integrated in some way. 
Recently, I did encounter a similar problem with SharePoint (based on 
Microsoft Internet Information Services). It seems that the IIS doesn't 
escape the URI in DAV:href tags too.

Regards, Tobias



On 06/22/09 14:00, Joe Orton wrote:
> On Fri, Jun 19, 2009 at 04:12:36PM -0500, Mark Jenkins wrote:
>> The patch allows a user of the ne_207 module to add in a hook for the  
>> moment where these unparsable DAV:href values are encountered. The user  
>> specified handler can then:
>>  * tell ne_207 to do what it usually does, ignore the bad href
>>  * fix the href, call uri_parse, and tell ne_207 that all is fine now
>> or
>>  * tell ne_207 that the situation is catasrophic. raise this as a  
>> serious error
> 
> Hi Mark, thanks for sending in the patch.
> 
> I appreciate the effort you've gone to here, but I think that is *way* 
> too much complexity to add to neon to work around an bug in one DAV 
> server implementation.
> 
> I'm not sure I see anything in neon that is appropriate to change for 
> this. The only thing I could see would be to have a way to propagate up 
> the error from a URI parse failure.
> 
> Regards, Joe
> 
>