BTW, I forgot to mention that my template contains the following HTML:
<form action="/forgotUserName2" method="post">{% csrf_token %}
<label for="id_email">E-mail:</label></th><td><input id="id_email"
type="text" class="required" name="email" maxlength="75" />
<input type="submit" value="Submit" />
</form>
On Tuesday, January 8, 2013 6:44:49 PM UTC-5, Saqib Ali wrote:
>
>
> Hi.
>
> I have been using Django successfully for a few days now. I was running my
> django application on an Amazon Web Service machine.
> I was assigned some arbitrary DNS name that looked like this:
> http://ec2-XXX.XXX.XXX.XXX.compute-1.amazonaws.com.
> My Django app was working find with my model and several views with
> templates.
>
> Last night, I went out and bought a real DNS name from register.com and
> have that DNS name now pointing to my django application.
> Since I made that change however, when I submit my django form, I get the
> following CSRF error:
>
>
> Forbidden (403)
>
> CSRF verification failed. Request aborted.
>
>
>
> I tried clearing the cookies in my browser, but that didn't help. I even
> tried it from other machines that I had never tried before. But still the
> same problem.
>
> Why did assigning a new DNS name for this IP address cause this CSRF
> error? And how do I get rid of it?
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/bfNeyTDIf2AJ.
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.
