Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 2
    "Page that used post data cannot be bookmarked": well, that's an advantage, no? You probably don't want your data-altering query to be bookmarked. Commented Jun 3, 2009 at 10:11
  • I suppose if every time post was used you were using it for a security driven purpose then this would be an advantage. Usually it is, but there is that length limit on GET. Maybe, somebody is just passing a ton of non-security related data and would like the page to be bookmarked? Who knows... Commented Jun 3, 2009 at 10:43
  • Regarding a disadvantage of GET, namely that "Variables are pased through url as name-value pairs", would MVC eliminate that issue because of routing and the resultant friendly URLs? Commented Jun 29, 2011 at 22:06
  • @MrBoJangles: Using nice URLs does not prevent the 'person looking over shoulder' risk referred to. Side note: MVC does not require routing with nice URLs and routing with nice URLs does not require MVC; they are sometimes used together, but can also be used separately. Commented Jul 28, 2012 at 5:15
  • In the .NET world, for all practical purposes, nice url capability = MVC. I suppose you could do some IIS rewrites or some weird code-based ones but they're even less pleasant. MVC, needless to say, for the win. Commented Jul 30, 2012 at 14:29