On Tue, 2011-06-14 at 15:36 +0200, Masklinn wrote:
> >> that would mean, that none of your website was ever reachable by
> >> entering the URL in a browser. Remember: all links you put on a
> >> webpage will be GET requests made by the browser, when you click on
> >> them.
> > lets put it this way
On Tue, Jun 14, 2011 at 2:03 PM, Kenneth Gonsalves
wrote:
> On Tue, 2011-06-14 at 08:51 -0400, Steven L Smith wrote:
>> POST should only be used for things that change stuff on the server...
>> a contact form, a form that creates something in a database, etc...
>
> thanks - in 15 years of web prog
On 2011-06-14, at 15:26 , Kenneth Gonsalves wrote:
> On Tue, 2011-06-14 at 15:10 +0200, Ivo Brodien wrote:
>>> thanks - in 15 years of web programming I have never used get -
>> maybe
>>> time to start now.
>>
>> ??
>>
>> that would mean, that none of your website was ever reachable by
>> enterin
On Tue, 2011-06-14 at 15:10 +0200, Ivo Brodien wrote:
> > thanks - in 15 years of web programming I have never used get -
> maybe
> > time to start now.
>
> ??
>
> that would mean, that none of your website was ever reachable by
> entering the URL in a browser. Remember: all links you put on a
>
> thanks - in 15 years of web programming I have never used get - maybe
> time to start now.
??
that would mean, that none of your website was ever reachable by entering the
URL in a browser. Remember: all links you put on a webpage will be GET requests
made by the browser, when you click on
On Tue, 2011-06-14 at 08:51 -0400, Steven L Smith wrote:
> For your use case, I would definitely use GET. The user may wish to
> bookmark the report, for example, or send it to a colleague. Searches
> and such should always use GET, unless there's a truly compelling
> reason not to.
>
> POST shoul
Monday, June 13, 2011 12:45:39 PM GMT -05:00 US/Canada Eastern
Subject: GET vs POST for read-only views
Is there a consensus in the community that GET should be used for
requests that don't write to the database? As a specific example, let's
say there's a report form that allows a
On 2011-06-13, at 18:45 , Shawn Milochik wrote:
> Is there a consensus in the community that GET should be used for
> requests that don't write to the database? As a specific example, let's
> say there's a report form that allows a user to select a start and end
> date, and maybe some other search
Is there a consensus in the community that GET should be used for
requests that don't write to the database? As a specific example, let's
say there's a report form that allows a user to select a start and end
date, and maybe some other search fields. What would you use for this,
and why?
I use PO
9 matches
Mail list logo
