Have you read the entire Note under
https://docs.djangoproject.com/en/1.4/topics/http/file-uploads/#modifying-upload-handlers-on-the-flywhich
discusses how the CSRF protection accesses request.POST and therefore
prevents changing upload handlers in a view which is CSRF protected? It
includes an exa
Looking at the docs...
https://docs.djangoproject.com/en/1.4/topics/http/file-uploads/
under "Modifying upload handlers on the fly"
it states:
"Sometimes particular views require different upload behavior. In these cases,
you can override upload handlers on a per-request basis by modifying
requ
On Oct 20, 2008, at 8:11 AM, truebosko wrote:
> What is happening: The custom upload handler works, data is being
> sent, the session is being set WITHIN the handler but when I call the
> function from Javascript to fetch the progress (or even from a simple
> manual GET) it does not return anythi
As I said in my post, I put it up on a non-dev server (lighttpd/fcgi
setup with mediatemple) because I know dev server can't handle it.
On Oct 20, 11:56 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> truebosko wrote:
> > What I found though, is that the view that is being called from JS
> > will
truebosko wrote:
> What I found though, is that the view that is being called from JS
> will finally have access to the session variable after the upload is
> complete
Looks like you're doing it with development server. It's single-process
and can't handle and upload and another view simultaneou
Hi there,
I wrote a previous post but I have discovered a bit more since. Here's
my situation:
What I'm trying to do: Write a custom upload handler that allows me to
intercept it with Javascript calls and return a simple progress upload
bar to the user.
What is happening: The custom upload hand
6 matches
Mail list logo
