Precisely, I wrote Sun to clarify this point some days ago but haven't
received a response yet. I have looked at various RFCs (1867, 2068,
2183, 2184, 2388) but found nothing of interest there, though I admit
that due to the speed reading these documents it is perfectly possible
that I missed something.
My opinion is that if a parameter contains an empty string, the
getParameter* should return null too. The behavior of browsers is
confusing, too, as an empty form field may be omitted or sent (as empty
string) depending for example on JavaScript being used or not.
Carlos Amengual
Nic Ferrier wrote:
>
> >>> Henric Larsson <[EMAIL PROTECTED]> 4/20/99 9:21:20 PM >>>
> >what should it return if the request came from a POST
> >but the value was not filled out in a form, also if the
> >parameter is present in a GET but no value is specified
> >for it.
>
> >I keep checking my parameters for a null and then for a
> >zero length String, I think the spec. should specify this
> >to ease the code up a bit.
>
> >if this is specified somewhere else like the http 1.0 spec.
> >could someone please let me know.
>
> I believe it is specified in HTTP/1.1. It's late here so I can't be
> bnothered to look it up /8->
>
> But I'm sure it there! I *think* that GET has preference.
>
> Certainly I think this beyond servlet specification, isn't it Sun?
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
