Response Body is not captured directly

jbrozenick / httpfox

Automatically exported from code.google.com/p/httpfox

GNU General Public License v2.0

0 stars 0 forks source link

Response Body is not captured directly #6

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

the body of the response is read from the cache. therefore if there are
requests which does not get cached it is not possible to view the content.
alternatives to getting the body/content would be nice.

Original issue reported on code.google.com by pappkame...@gmail.com on 5 Mar 2008 at 10:40

GoogleCodeExporter commented 9 years ago

Original comment by pappkame...@gmail.com on 9 Mar 2008 at 11:32

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

I've noticed the same problem, and it makes it very hard to debug webservice 
responses.

I would say this is a HIGH priority issue, and I can help test anything if 
needed.

Original comment by jrse...@gmail.com on 10 Sep 2008 at 6:17

GoogleCodeExporter commented 9 years ago

I agree - when a request to a webservice returns a 500 and an error code, I 
cannot
view the response to see what the error actually is 
(NS_ERROR_DOCUMENT_NOT_CACHED or
some such).  It basically renders the plugin useless!  Or perhaps there is a
workaround to force FF to cache these responses too!

Original comment by ekpet...@gmail.com on 18 Nov 2008 at 10:48

GoogleCodeExporter commented 9 years ago

Same here.

Original comment by hikaritokyo on 8 Feb 2009 at 2:52

GoogleCodeExporter commented 9 years ago

This should use nsITraceableChannel interface to intercept the content, this is 
more
reliable than getting data from cache.

Original comment by wladi...@palant.de on 11 Jun 2009 at 8:22

GoogleCodeExporter commented 9 years ago

yes, using nsITraceableChannel is planned.

Original comment by pappkame...@gmail.com on 12 Jun 2009 at 7:14