Yes, that fixes it!  Many thanks, Chris!

        - Allan


On Tue, 22 Feb 2011, Chris Moffitt wrote:

Try adding theclient_max_body_size directive to your nginx conf-

http://wiki.nginx.org/HttpCoreModule#client_max_body_size

-Chris

On Tue, Feb 22, 2011 at 4:34 PM, Allan Stavely <[email protected]> wrote:


I'm running nginx.

I don't see anything in my nginx configuration file that would put a limit
on the size of a file, as far as I know.

I do have a workaround, obvious but clumsy:

1.  When adding the product, upload a small dummy PDF file.
2.  Transfer the real file to the shop's file system myself.
3.  Substitute the real file for the dummy file in static/protected/,
       giving it the same name.

Will this do everything necessary?  It seems to work so far.

I would like to find a cleaner solution, of course.

Thanks, Chris,

       - Allan



On Tue, 22 Feb 2011, Chris Moffitt wrote:

 What web server configuration are you using? Sometimes this is a limit
imposed by your server - it's not normally a django/satchmo issue.

-Chris

On Tue, Feb 22, 2011 at 11:22 AM, allan <[email protected]> wrote:

 Hello all,

I'm trying to create a downloadable product, which will be a rather
large PDF file: a whole book, 5+ megabytes.  When I try to upload the
file on the admin "Add Downloadable Product" page, my browser freezes
waiting for a response, and I get this in my errors log:

2011/02/22 09:40:45 [error] 1928#0: *3469 client intended to send too
large body: 5271910
 bytes,  [ ... ] request: "POST /admin/downloadable/d
ownloadableproduct/add/ HTTP/1.1", [ ... ]

Suggestions?  I can easily copy the file myself to the machine that's
running my store.  Is there a way to get the content to the right
place without having it go through the HTTP POST?

Thanks,

  - Allan

--
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
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/satchmo-users?hl=en.



--
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
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/satchmo-users?hl=en.



--
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
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/satchmo-users?hl=en.



--
You received this message because you are subscribed to the Google Groups "Satchmo 
users" group.
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/satchmo-users?hl=en.



--
You received this message because you are subscribed to the Google Groups "Satchmo 
users" group.
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/satchmo-users?hl=en.

Reply via email to