Re: GET vs POST for read-only views

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

Re: GET vs POST for read-only views

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

Re: GET vs POST for read-only views

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 >>

Re: GET vs POST for read-only views

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 >

Re: GET vs POST for read-only views

> 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

Re: GET vs POST for read-only views

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

Re: GET vs POST for read-only views

googlegroups.com Sent: 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 th

Re: GET vs POST for read-only views

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

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 user to select a start and end date, and maybe some other search fields. What would you use for this, and why? I use

Re: get vs. post in production vs. dev server

I forgot to mention my development server is fastcgi/apache. Thnaks On Feb 21, 11:15 am, Josh Cartmell wrote: > I have a simple login form on every page like this: > > {% csrf_token %} > > type="password"> > > > > It was working great on the dev server.  Then I went into

get vs. post in production vs. dev server

I have a simple login form on every page like this: {% csrf_token %} It was working great on the dev server. Then I went into production. Now every form submission is being interpreted as a GET rather than a POST unless I am actually on the page /shop/account/ (the forms action). Has

Re: GET vs POST?

On Sat, Mar 14, 2009 at 4:54 PM, ihome wrote: > > Hi, > > I defined a form to load data from HttpRequest in views.py. For the > same function, sometimes, I need to pass a POST request while some > times I need to pass in a GET request. > > For POST, I used > >

GET vs POST?

Hi, I defined a form to load data from HttpRequest in views.py. For the same function, sometimes, I need to pass a POST request while some times I need to pass in a GET request. For POST, I used MyForm(request.POST) to load the data and it works well. For GET method, MyForm(request.POST)