I haven't dug around in Django enough to know if there is a Django
solution, but from the database side a view might do what you want? I
have not tried this myself.
http://msdn.microsoft.com/en-us/library/ms187956.aspx
So define a view that follows the Django naming convention, backed by
a table t
@etone: has this discussion of CSRF enabled you to hunt down your
problem?
Steven.
On Jul 26, 4:30 pm, etone wrote:
> Hi there,
>
> I'm trying to sent a HTTP POST from a client application to my Django
> app. Django does indeed receive the HTTP POST as I do hit
> _HandleRequest(), however it r
If it is a CSRF issue, then perhaps using this setting will help you
get to the bottom of what's going on:
http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#rejected-requests
As it says there, a 403 may be due to a lack of the {% csrf_token %}
in the form that is being posted.
Steven.
--
Yo
> So I should be looking at SESSION_COOKIE_SECURE (http://
> docs.djangoproject.com/en/dev/topics/http/sessions/)?
Cookies are passed along with the request, not in a separate
connection. Therefore with browsers that support secure only cookies,
setting SESSION_COOKIE_SECURE = True would require a
It's a very common pattern to use SSL for login and private profile
details and then have the cookie passed over an unencrypted channel
for the rest of the site.
I have implemented an approach where nginx handles all the SSL and
proxies requests to apache (which directly serves non-SSL requests).
Thanks Dimitry,
> If you want space to take part in comparison, use char fields instead of
> varchar. See:http://dev.mysql.com/doc/refman/5.0/en/char.html
The below quote from the reference link you sent would seem to
indicate that trailing spaces *do not* take part in the comparison in
char fiel
6 matches
Mail list logo
