Adam Stegman wrote:
> Also, a GET is just a read, while a POST is used to create. Like the
> Wikipedia article linked before says:
>> Note that GET should not be used for operations that cause side-effects,
>> such as using it for taking actions in web applications.
Thanks guys this really helped
Also, a GET is just a read, while a POST is used to create. Like the
Wikipedia article linked before says:
> Note that GET should not be used for operations that cause side-effects, such
> as using it for taking actions in web applications.
On Aug 2, 12:33 am, ct9a wrote:
> GET
> - typically use
To add, in relation to a GET request, there is a limit of number of
characters that a url can be made of.
http://stackoverflow.com/questions/1496080/limitation-of-url
Cheers
Gordon Yeong :)
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group
GET
- typically used when you access a page via a link (ie you cut and
paste into the web browser)
- all the values (ie form arguments) get passed in the url itself
( delimited by the ampersand character)
- example: when the following link is copied and pasted to the web
browser, a GET request is g
4 matches
Mail list logo
