OT: No web-jsptaglibrary_2_2.xsd?

2013-03-01 Thread Nick Williams
General question for all the Tomcat developers out there, but I'm betting Mark has the best shot at answering: Perusing the Tomcat sources I noticed that there are JSP tag library XSD files web-jsptaglibrary_1_1.xsd, web-jsptaglibrary_1_2.xsd, web-jsptaglibrary_2_0.xsd and web-jsptaglibrary_2_1

svn commit: r1451777 - in /tomcat/tc7.0.x/trunk: ./ webapps/docs/changelog.xml webapps/docs/tomcat-docs.xsl

2013-03-01 Thread kkolinko
Author: kkolinko Date: Fri Mar 1 23:38:03 2013 New Revision: 1451777 URL: http://svn.apache.org/r1451777 Log: Merged revision 1451769 from tomcat/trunk: Disable comments section for the "Changelog" page. This fixes JavaScript errors when viewing changelog as XML file in a browser. (I suspect that

svn commit: r1451769 - in /tomcat/trunk/webapps/docs: changelog.xml tomcat-docs.xsl

2013-03-01 Thread kkolinko
Author: kkolinko Date: Fri Mar 1 23:25:19 2013 New Revision: 1451769 URL: http://svn.apache.org/r1451769 Log: Disable comments section for the "Changelog" page. This fixes JavaScript errors when viewing changelog as XML file in a browser. (I suspect that is because you cannot use document.write()

Re: URIs, %nn decoding and error handling

2013-03-01 Thread Remy Maucherat
On Fri, 2013-03-01 at 20:36 +, Mark Thomas wrote: > I expect to have a similar discussion about request bodies once URIs are > resolved where I have essentially the same view - a decoding error > should lead to a request failure. > > Thoughts? It may not be useful. UTF-8 is THE most used en

Re: URIs, %nn decoding and error handling

2013-03-01 Thread Konstantin Kolinko
2013/3/2 Mark Thomas : > Due to bug 54602 [1] I have been writing some test cases to examine how we > handle invalid bytes sequences in URIs. > > My expectation was: > - valid byte sequence for expected encoding -> 200 (assuming no other > problems) > - invalid byte sequence for expected encoding

URIs, %nn decoding and error handling

2013-03-01 Thread Mark Thomas
Due to bug 54602 [1] I have been writing some test cases to examine how we handle invalid bytes sequences in URIs. My expectation was: - valid byte sequence for expected encoding -> 200 (assuming no other problems) - invalid byte sequence for expected encoding -> 400 - partial byte sequence fo

[Tomcat Wiki] Trivial Update of "JoanV24" by JoanV24

2013-03-01 Thread Apache Wiki
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "JoanV24" page has been changed by JoanV24: http://wiki.apache.org/tomcat/JoanV24 New page: They call me Elwood but I never really liked that phone.<> What I really enjoy doing is d

[Tomcat Wiki] Trivial Update of "KatriceUp" by KatriceUp

2013-03-01 Thread Apache Wiki
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "KatriceUp" page has been changed by KatriceUp: http://wiki.apache.org/tomcat/KatriceUp New page: Friends call her Shawnda Barreras. To play domino is the thing she loves most rega

[Bug 54602] B2CConverter character decode underflow leaves bytes in buffer

2013-03-01 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54602 --- Comment #7 from Mark Thomas --- (In reply to comment #5) > Where do you think I started talking about request bodies? Sorry about the confusion. You were looking at 7.0.x and I was looking at trunk. When you mentioned an InputStream I

[Bug 54602] B2CConverter character decode underflow leaves bytes in buffer

2013-03-01 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54602 --- Comment #6 from Remy Maucherat --- Yes, this is confusing to you probably. Your problem with URI processing and trunk was that I forgot to port a call to recycle, which likely caused a problem there [and you can ignore the rest, it does