I tried to publish a bunch of media files all pdfs and i got error:
IIS 10.0 Detailed Error - 413.1 - Request Entity Too Large
This error occurs when the Web server receives a large amount of data from the client. It also occurs if client certificate negotiation occurs while receiving a large request.
Not something todo with maxrequest length in web.config?
yeah in this beta we haven't changed the default length (so if the zip file is over approx 5mb will probably error in default settings. ).
We have been experimenting with this, we think the following in the web.config will just up the limit for the receive endpoint (in this case 200mb i think) without updating everything else.
That worked a treat just published 100 pdfs no issues. One thing, currently i am running locally. However we are potentially looking to use this for a new client site will be on azure and media will be in blob storage. We will have azure blob storage filesystem provider so I am guessing it should all still work?
First glance at this and i am really excited it looks amazing.
the media is all going in and out via the mediaService APIs so should obey the blob storage settings
it will also write files to the temp folder as part of the process, but for this will obey the EnviromentTemp settings and so write to the faster localtemp folders on an AzureWebApp.
we've done some basic tests on all this but we haven't tested this in anger yet.
Error when moving media
Hello,
I tried to publish a bunch of media files all pdfs and i got error:
Not something todo with maxrequest length in web.config?
Hi,
yeah in this beta we haven't changed the default length (so if the zip file is over approx 5mb will probably error in default settings. ).
We have been experimenting with this, we think the following in the web.config will just up the limit for the receive endpoint (in this case 200mb i think) without updating everything else.
Kevin,
That worked a treat just published 100 pdfs no issues. One thing, currently i am running locally. However we are potentially looking to use this for a new client site will be on azure and media will be in blob storage. We will have azure blob storage filesystem provider so I am guessing it should all still work?
First glance at this and i am really excited it looks amazing.
Regards
Ismail
yes, it 'should' :)
the media is all going in and out via the mediaService APIs so should obey the blob storage settings
it will also write files to the temp folder as part of the process, but for this will obey the EnviromentTemp settings and so write to the faster localtemp folders on an AzureWebApp.
we've done some basic tests on all this but we haven't tested this in anger yet.
Kevin
is working on a reply...