struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hookom, Jacob" <Jacob.Hoo...@redline.mckhboc.com>
Subject RE: [OT] Anatomy of a long URL
Date Mon, 28 Jun 2004 14:20:36 GMT
Not if it's a POST.

Example, we had a page that allowed you to modify multiple items at once in
a list and submit them via a GET.  This worked fine in testing.  As
customers started to use the app, their list of items got very large and the
data submitted got much larger-- a much longer URL being submitted.  But, it
stopped working for some customers.  After some investigation, we realized
the we couldn't use a GET because the URL was too long.  Changing to a post
fixed it.  I believe the max length is 256.

GET:
/app/updateItems.do?0di=2,4,92,10&1di=4,23,45,12&usr01=432,43,22,4 ....

POST:
/app/updateItems.do  (all the data isn't encrypted in the URL)




-----Original Message-----
From: Rick Reumann [mailto:struttin@reumann.net] 
Sent: Monday, June 28, 2004 9:11 AM
To: Struts Users Mailing List
Subject: Re: [OT] Anatomy of a long URL

Hookom, Jacob wrote:

> Another example is JSF.  JSF allows you to store your state client side or
> server side.  If it's client side, your buttons, etc become POSTs instead
of
> GETs in order to get around the URL length limit.  Also, hidden fields are
> written out with your objects serialized into a string that you repost
next
> time you click a link on the page.

I thought there was a limit to how large URLs can be (maybe that's a 
server limitation though?).. wouldn't the above potentially cause problems?

-- 
Rick

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
View raw message