The reasons for redirecting depend on what the view is doing. The "resend-data-on-POST" problem was already mentioned but then the view could take other measures to prevent information from being submitted twice.
There is also the reason of URL consistency and hygiene. A URL (or URI to be precise), by definition, is meant to represent exactly one specific document on the web. It is not a good idea to put two or more different documents in the same place, or have the same document accessible on two different URLs. Of course, the definition of what different documents are depend on the application. So, instead of rendering the same document in two places, have one canonical place and redirect there. Also, it might be interesting to look at the different kinds of redirection that HTTP offers (3xx status codes). http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Henning -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/KS9f0iZ4Wi0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
