cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

File size limit for webdav upload

Former Member
0 Kudos
1,070

Dear Experts,

we set up what we thought to be a restriction of the file size allowed for upload. We did this in the portal via

System administration --> system configuration --> Knowledge Management --> Protocols --> WebDav --> Max WebDAV request size: 15728640 bytes.

We would have expected that to not allow us uploading any files larger than 15 MB. Turns out we were wrong and it does not work. Here is a http-trace of an upload of a 21 MB file.

Note the content length in the outbound message is 21832627.

========= Outbound Message =========
PUT /irj/go/km/docs/documents/LSO/WBT/Academy_test_area/upload/secondUpload/SCORM%5B1%5D.2004.3ED.DocSuite.zip/SCORM%5B1%5D.2004.3ED.DocSuite.zip HTTP/1.1
Host: ****hostname****:443
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: UCI DAV Explorer/0.91 RPT-HTTPClient/0.3-3E
Translate: f
Cookie: j_authscheme=basicauthentication; saplb_*=(J2EE405983900)405983952; JSESSIONID=(J2EE405983900)ID1262004252DB00846306331792142983End
Cookie2: $Version="1"
Authorization: Basic NDkwNjIyNzE6TGVybnRlNzg=
Accept-Encoding: deflate, gzip, x-gzip, compress, x-compress
Content-type: application/zip
Content-length: 21832627


**** Lots of Content ****

* 21 MB of bits and bytes

**** / Lots of Content


========= Inbound Message =========
HTTP/1.1 201 Created
Date: Wed, 19 Aug 2009 15:39:07 GMT
Server: SAP J2EE Engine/7.01
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache
Vary: accept-encoding,accept-language,cookie,translate
ETag: "1589137901012"
Last-Modified: Wed, 19 Aug 2009 15:39:15 GMT
Content-Length: 0
Via: 1.1 ****hostname****:443

Would anyone know any other way of preventing the upload of large files via a webDAV client?

Thank you very much.

Regards

Michael

View Entire Topic
Former Member
0 Kudos

That property only applies to WebDAV requests such as PROPFIND, PROPPATCH or REPORT. PUT is part of the base HTTP/1.1 protocol.

There are other places you could try to enforce the limit, such as in the servlet engine itself (doesn't NetWeaver a limit for all requests...?).