Any reason why FORM "POST" is used and not "GET"

+2 votes
I would be using WikiTree a lot more if it's searches were more friendly and I could search for and bookmark matches, (by URL) as an example:
in WikiTree Tech by Dennis Bareis G2G Crew (410 points)
retagged by Dennis Bareis
you need to add tags for Sysops for that group to answer a system question
Thanks just added tags, went to a "system" group so I'd have expected it to go where it should but oh well, that's for letting me know.

1 Answer

+1 vote

In reference to W3Schools (page link)...

GET requests:

  • GET requests can be cached
  • GET requests remain in the browser history
  • GET requests can be bookmarked
  • GET requests should never be used when dealing with sensitive data
  • GET requests have length restrictions
  • GET requests are only used to request data (not modify)

POST requests:

  • POST requests are never cached
  • POST requests do not remain in the browser history
  • POST requests cannot be bookmarked
  • POST requests have no restrictions on data length

That should shed some light on why POST is being used

by Richard Shelley G2G6 Pilot (220k points)
I knew most of that, I have no issue with caching of the data, I can refresh if required, the length is unlikely to be an issue and there is no sensitive information, so no, that doesn't say why.

Another variation is to support the get parameter where the post doesn't exist, many sites do that.  That is the best of both worlds.

Related questions

+10 votes
4 answers
142 views asked Aug 28, 2017 in Genealogy Help by Dennis Wheeler G2G6 Pilot (537k points)
+3 votes
0 answers
+10 votes
2 answers
144 views asked Nov 16, 2019 in The Tree House by Susan Keil G2G6 Mach 6 (60.1k points)
+3 votes
2 answers
+14 votes
4 answers
+10 votes
1 answer
166 views asked Aug 13, 2018 in WikiTree Tech by Anonymous Cowan G2G6 (8.7k points)
+6 votes
0 answers
+2 votes
1 answer

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright