5,838
edits
Webtags (preserving history): Difference between revisions
Webtags (preserving history) (view source)
Revision as of 11:32, 5 August 2020
, 11:32, 5 August 2020→"POST" approach
| Line 762: | Line 762: | ||
The post approach has a few advantages over get: | The post approach has a few advantages over get: | ||
*The parameters are not shown in any query-string, so are not obvious to the person looking over your shoulder, nor do they appear in a history list of sites that the browser has visited. | *The parameters are not shown in any query-string, so are not obvious to the person looking over your shoulder, nor do they appear in a history list of sites that the browser has visited. | ||
*If you fill out a form online, the post approach will be used as the content needs to be kept secure. The get approach may be seen when you are navigating through a web site, and a selection is being remembered. | *If you fill out a form online, the post approach will be used as the content needs to be kept secure. | ||
* | **The get approach may be seen when you are navigating through a web site, and a selection is being remembered. | ||
*The POST approach can handle very long requests and return a lot of information. | |||
**In contrast, a URL with query-string is restricted in total length (the restriction is dependent on a number of other factors, but might be at something like 1000 characters in total), so GET comes with a restriction on how many parameters can be specified. | |||
here is an example text file with some web tags in it, let us store it in '''process.txt''': | here is an example text file with some web tags in it, let us store it in '''process.txt''': | ||