Re: satchmo SSLRedirectMiddleware for /admin not working with 1.1.1
Hi
Still chasing this one, and it seems that POSTs in the admin will use
http, not https when posting. Looking at the admin template, the
action is {{ form_url }} - this seems to be None, I was wondering
about using something like request.HTTP_REFERER in there, to make sure
it stays on https - any clues?
Thanks,
On 27 Oct, 15:48, captainmish <captainm...@gmail.com> wrote:
> Hello
>
> First apologies for cross-posting, this is also a discussion in
> satchmo-users.
>
> I am trying to secure admin urls using satchmo's (0.9)SSLRedirectMiddleware,
> using HTTPS_PATHS in settings. It works
> perfectly in django 1.1, but breaks in 1.1.1 with "Django can't
> perform a SSL redirect while maintaining POST data. Please structure
> your views so that redirects only occur during GETs."
>
> I guess my job is now to look at what changed in this update and
> figure out what is causing this, but hoping that someone else may be
> able to help or give some tips on this!
>
> Any thoughts/tips/RTFMs welcome!
>
> Thanks,
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
satchmo SSLRedirectMiddleware for /admin not working with 1.1.1
Hello First apologies for cross-posting, this is also a discussion in satchmo-users. I am trying to secure admin urls using satchmo's (0.9) SSLRedirectMiddleware, using HTTPS_PATHS in settings. It works perfectly in django 1.1, but breaks in 1.1.1 with "Django can't perform a SSL redirect while maintaining POST data. Please structure your views so that redirects only occur during GETs." I guess my job is now to look at what changed in this update and figure out what is causing this, but hoping that someone else may be able to help or give some tips on this! Any thoughts/tips/RTFMs welcome! Thanks, --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
authenticated CDN content
Hello We have been using a view that implements X-Sendfile (with apache's mod_xsendfile) to serve content to authorised users, but now need to switch to cloudfiles. Cloudfiles doesnt offer any kind of authentication, so we'll need to implement it in django / apache somehow. What I have done is just change the view (decorated with user_passes_test) to return an HttpResponseRedirect for the CDN content, this works but I was hoping someone had come up with something smarter than this. Once someone has the CDN url of a file, they can pass it around etc. It seems we cant use X-Sendfile for non- local files (please let me know if I'm wrong!), so not really sure what else to try. Any tips very welcome! Thanks, --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
FilePathField refresh
Hello Im trying to implement an "alternative upload" method for getting big files into my django app - and was hoping to allow users to scp/rsync etc files to the server, then use FilePathField to browse them and use them to make objects with FileField. The files are all shown in the path specified and work fine, but the problem comes in seeing new files - the server needs to be reloaded before any new files are shown in the filepathfield select... Is there a workaround for this, or an alternative way of doing it? Thanks, --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
