jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben" <apa...@benmeadowcroft.com>
Subject RE: DO NOT REPLY [Bug 25497] New: - Input tags generate invalid XHTML,
Date Sun, 14 Dec 2003 21:16:33 GMT
> This is hearsay, but I've always used the GET/POST versions 
> due to being told a while back that certain servers were case 
> sensitive on the uppercase version. I'm not sure which 
> servers they were though, but that could be a reason to use 
> the uppercase variant.

The method *is* case sensitive for the server (it should be uppercase)
See 5.1.1. http://www.faqs.org/rfcs/rfc2616.html

However what we are talking about here is a client side issue, not a
server side issue. The client should always send the method in
uppercase, GET, POST etc... However the client determines the method
from the HTML form to send the request, and the HTML method identifier
is case insensitive for HTML 4.01 and lowercase for XHTML.

Using the lowercase "get" is valid HTML and valid XHTML. I am working on
a commercial project which requires valid XHTML compliance which is why
I have raised this bug. I have "fixed" this on the version of the input
taglibs on my server so whether the patches get put in or not doesn't
bother me really (although it may make future maintenance easier).
However I think that producing valid X/HTML is a worthwhile goal and is
important for many projects. Additionally I think that compatibility
concerns, both current and future, are best addressed through following
formal standards where applicable.

P.S. I've used action="get" a few times, it should have been
method="get", sorry for any confusion caused.

To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org

View raw message