Kbase 20475: Limitations With Forms Using Get (WebSpeed) - How much information can be stored in a browsers addre
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
How much information can be stored in a browsers address bar
GOAL:
What is the limitation is in the amount of information your browser can process in the address bar and is not a WebSpeed limitation.
FIX:
Your address bar might have a limit to the number of characters it can contain and therefore excludes the remaining information you are passing to your browser. (Internet Explorer 5.)
This limitation can rectified by changing the form's method from "GET" to "POST". In a form, "GET" passes data as part of the URL, while a "POST" passes data through the Agent's standard input.
"GET" : passes data as part of the URL,
"POST" : passes data through the Agent's standard input.
When the POST method is used, process-web-request, calls the inputFields procedure by default. The inputFields procedure loads the form buffer with input by running the get-value function for every field on the form.
note:
That process-web-request runs a different sequence of processes depending on whether the HTML Form METHOD attribute is GET or POST.
GET:
Data from the client request is appended to the URL of the Web object. Usually, GET code processes the first request and returns a blank form.
POST:
Data is sent to the Web object as a separate stream. Usually, POST code processes subsequent requests.