Get vs Post

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Gittins Gal replied

6 January 2014, 23:39
Originally posted by SpontaneousOrder View Post

Is the postcode in the query string used to retrieve a resource? E.g. load up a list of addresses at that postcode? If so then a GET sounds about right to me.

The implied semantics of the http protocol (not that i'm saying you should necessarily following them) are GETs for retrieving resources, POSTs & PUTs for modifying/adding resources, DELETEs for deleting (if your web server does DELETEs) etc.

There might be perfectly good reasons to use a POST, but without knowing them it seems more 'proper' to use a GET (assuming my original assumption/guess was correct).

Yes, your assumptions are correct. Thank you SO
Leave a comment:
SpontaneousOrder replied

6 January 2014, 22:53
Originally posted by Gittins Gal View Post

Ive just been completely stumped by a question a permie has asked me (please bear with me - I'm primarily a SQL dev).

I have a page that redirects to another page passing a postcode on the query string. Pretty standard stuff but he asked me why I'm doing a get instead of a post. And I couldn't really answer him.

Is the postcode in the query string used to retrieve a resource? E.g. load up a list of addresses at that postcode? If so then a GET sounds about right to me.

The implied semantics of the http protocol (not that i'm saying you should necessarily following them) are GETs for retrieving resources, POSTs & PUTs for modifying/adding resources, DELETEs for deleting (if your web server does DELETEs) etc.

There might be perfectly good reasons to use a POST, but without knowing them it seems more 'proper' to use a GET (assuming my original assumption/guess was correct).
Leave a comment:
darrylmg replied

6 January 2014, 21:34
Post can sort of hide the data from the url, which is cleaner in my eyes.
If you need to use SSL then the url is not encrypted, but the data in a post is.
Leave a comment:
fullyautomatix replied

6 January 2014, 17:52
Originally posted by Bunk View Post

Whichever one is on the link that they crawl.

And in this instance that URL does not exist. I mean Google has intelligence but not so much that it can input post code and crawl a URL.

Anyway, POST makes sense if the data is quite huge since QS has a limit. Advantage of GET is that the URL can be directly loaded without the need to re post the data.
Leave a comment:
Bunk replied

6 January 2014, 17:08
Originally posted by VectraMan View Post

What postcode does a search bot use?

Whichever one is on the link that they crawl.
Leave a comment:
VectraMan replied

6 January 2014, 16:51
Originally posted by Unix View Post

One of the advantages of using the GET method is you can bookmark the URL and search engines will crawl your page and index it. With a post this cannot happen.

What postcode does a search bot use?
Leave a comment:
Unix replied

6 January 2014, 13:47
One of the advantages of using the GET method is you can bookmark the URL and search engines will crawl your page and index it. With a post this cannot happen.
Leave a comment:
northernladuk replied

6 January 2014, 13:13
Originally posted by Gittins Gal View Post

I'm guessing that in this instance it doesn't matter and it is just a spurious question from a permie.

Possibly but sounds like you proved him right
Leave a comment:
Gittins Gal replied

6 January 2014, 13:08
Originally posted by minestrone View Post

If the page is using the postcode to make a different page for each postcode then it should by right have a unique URL with the postcode in it. So a Get.

That's the answer I needed earlier! It would have shut the permie up...
Leave a comment:
minestrone replied

6 January 2014, 12:59
If the page is using the postcode to make a different page for each postcode then it should by right have a unique URL with the postcode in it. So a Get.
Leave a comment:
Gittins Gal replied

6 January 2014, 12:43
Originally posted by Platypus View Post

Google's quite a handy tool. As an SQL dev perhaps you don't know about it?

HTTP Methods GET vs POST

Thanks. I think....
Leave a comment:
Platypus replied

6 January 2014, 12:20
Google's quite a handy tool. As an SQL dev perhaps you don't know about it?

HTTP Methods GET vs POST
Leave a comment:
Gittins Gal started a topic Get vs Post

6 January 2014, 12:18
Get vs Post

Ive just been completely stumped by a question a permie has asked me (please bear with me - I'm primarily a SQL dev).

I have a page that redirects to another page passing a postcode on the query string. Pretty standard stuff but he asked me why I'm doing a get instead of a post. And I couldn't really answer him.

This isn't sensitive data - is there any reason to use a post over a get in this scenario? Or for that matter a get over a post? I should imagine a post involves squirting more markup over the wire but I have an all encompassing form in the master page anyway so I can't really use that argument.

I'm guessing that in this instance it doesn't matter and it is just a spurious question from a permie.
Tags: None