Hi Malcolm,
I definitely am "starting out", I'm a complete web dev noob... but I
was under the impression that I was using GET & POST correctly.
I thought GET should be used when the action results in no state
change on the server side (e.g. retrievals, queries, etc) and POST was
used to alter the state of the server.
Is this correct?
If it is, then I think GET is appropriate here as I'm not storing any
of the data that the form is sending, the data is simply used to query
the db.
Thanks,
Alex
On Jan 8, 2:55 am, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Wed, 2009-01-07 at 11:12 -0800,rabbiwrote:
>
> [...]
>
> > I have a submit input on one of my pages and when I run the site on
> > runserver it still works fine (I just tried it now)
> > However, when I run the exact same site on Apache the url that is
> > returned by "submit" is different, and this obviously causes the
> > pattern matching in urls.py to fail
>
> That's not correct. See below.
>
>
>
>
>
> > Here is the html + template script that causes the problem
>
> > {% if error_message %}<p><strong>{{ error_message }}</strong></p>{%
> > endif %}
>
> > <form action="/swenglish/test/submit/" method="get">
> > {% for entry in entry_list %}
> > <label for="swe_question{{ forloop.counter }}">{{
> > entry.eng_val }}</
> > label>
> > <input type="text" name="{{ entry.eng_val
> > }}"/><br />
> > {% endfor %}
> > <input type="submit" value="submit" />
> > </form>
>
> > With runserver it returns the following when I press submit:
> > "http://127.0.0.1:8000/swenglish/test/submit/";
>
> > With Apache it returns the followingwhen I press submit:
> > "http://localhost/swenglish/test/submit/?thank
> > +you=tack&much=mycket&he=han&fun=roligt&bye=hej+da&snow=sno"
>
> I don't think this is the problem you think it is. URL pattern matching
> in Django doesn't look at the hostname portion of the URL or the query
> string (everything after the "?"). So those two URLs should look exactly
> the same to Django. When you have DEBUG=True in your settings file, do
> you really get the 404 screen saying it couldn't match any URL patterns?
> If so, what pattern does it say it was trying to match?
>
> It looks like something is going wrong in the runserver case, by the
> way. Your form is submitted using a GET action, which means the
> submitted URL should look like the second case (although the hostname
> portion might well be different). It's not clear why you're using GET
> and not POST there, by the way -- better to use normal form processing
> practice -- which means action="post", not action="get" -- when you're
> starting out so that the differences don't make things any harder than
> they already are.
>
> Regards,
> Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
