Klemens Muthmann wrote:
Didn't know this. I thought files would be part of the message content.
Well, in a well-behaved application using HTTP, they should be.
HTTP headers are generally meant to convey information /about/ the content, not to /be/
the content. Otherwise they would not be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 12/14/2010 5:05 AM, André Warnier wrote:
Klemens Muthmann wrote:
Didn't know this. I thought files would be part of the message content.
Well, in a well-behaved application using HTTP, they should be.
HTTP headers are generally meant
Hi,
I wrote a REST webservice that accepts file uploads to the server. I
used the Restlet framework and as long as I am running the application
on the internal Restlet Web Server everything works fine. However as
soon as I deploy my application as WAR to tomcat (tomcat 6.0.24) it
seems that
On 13/12/2010 16:03, Klemens Muthmann wrote:
Hi,
I wrote a REST webservice that accepts file uploads to the server. I
used the Restlet framework and as long as I am running the application
on the internal Restlet Web Server everything works fine. However as
soon as I deploy my application
Hm. It works. Great.
However I wonder why the parameter that allows me to upload a larger
block of ~CONTENT~ is called maxHttp~HEADER~Size.
Nevertheless. Thank you very much for your fast answer.
Am 13.12.2010 17:06, schrieb Mark Thomas:
On 13/12/2010 16:03, Klemens Muthmann wrote:
Hi,
I
On 13/12/2010 16:31, Klemens Muthmann wrote:
Hm. It works. Great.
However I wonder why the parameter that allows me to upload a larger
block of ~CONTENT~ is called maxHttp~HEADER~Size.
Because you are uploading data in the request headers, not in the
request body.
Mark
Nevertheless.
Didn't know this. I thought files would be part of the message content.
OK. Thanks for the explanation.
Am 13.12.2010 17:42, schrieb Mark Thomas:
On 13/12/2010 16:31, Klemens Muthmann wrote:
Hm. It works. Great.
However I wonder why the parameter that allows me to upload a larger
block of
