After checking the Fedora and Tomcat logs (and setting them to log everything),
there doesn't appear to be any difference between responses which return the
payload and those that do not.
Does anyone have any suggestions as to potential causes we could chase down?
I'm stumped as to what the trouble might be. The server is not under
significant load as we haven't gone live yet, so it doesn't look to be a
resource issue.
Thanks for any help.
Rob
From: Wolff, Robert
Sent: Monday, March 28, 2011 9:44 AM
To: fedora-commons-users@lists.sourceforge.net
Subject: Http response 200 but no payload?
Hi Everyone,
We're having an issue wherein Fedora/Tomcat will respond to a REST API-A
request with 200 and Transfer-Encoding: chunked but then sends no chunks.
Here's a typical response header:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Pragma: No-cache
Cache-Control: no-cache
Expires: Wed, 31 Dec 1969 19:00:00 EST
content-disposition: inline; filename="Annual report Town of Center Harbor New
Hampshire 2008.jpg"
Content-Type: image/jpeg
Transfer-Encoding: chunked
Date: Sun, 27 Mar 2011 01:46:23 GMT
...and that's it, no payload.
This might be a Tomcat issue, but has anyone seen this before? I thought I'd
check before pouring over the logs. We're running Fedora 3.4.2.
Thanks,
Rob
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
