[WG: Sakai QA] Webdav protocol inconsistencies between QA servers.

[Jean-Francois Leveque]

Hi all,

Alan, I think one of the differences related to mod_jk may come from the 
fact that the fix for http://jira.sakaiproject.org/browse/SAK-5075 has 
not been included yet even if reviewed and used by others than the lead 
for Webdav.

I've been using it since 2.4.x without problems in Apache HTTPD versions 
older than 2.2.8 (I currently use 2.2.3 with mod_proxy_ajp). Others than 
myself have commented that it's safe and advocated for its inclusion.

Is there any reason not to include this fix?

Maybe the Sakai version, Mod_jk and SSL information could be added with 
each server ID and we could sort by most failure-related parameters to 
get a better picture. What do you think, Alan?

Cheers,

J-F

Berg, A.M. a écrit :
> Hi all,
> 
> More for background information: I have checked various Sakai Qa servers 
> including nightly for webdav protocol compatibility via the litmus tool 
> and then parsed the results into an HTML table 
> (http://builds.sakaiproject.org/litmus/2010/1/). There is some variation 
> between servers due to what I assume is Sakai version, Mod_jk and SSL 
> connections and other unknown factors. Therefore, if you are debugging 
> webdav/browser issues it is well worth checking across a range of 
> relevant servers.
> 
> I will write a Jira that is unassigned and if anyone works towards 
> improving protocol consistency can then use it to act as an umbrella.
> 
> Alan
> 
> Alan Berg
> Interim QA Director - The Sakai Foundation
> 
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
> 
> http://home.uva.nl/a.m.berg