eZHTTPTool::parseHTTPResponse and chunked transfer encoding

Next topic

Author	Message
Marko Žmak	Monday 06 June 2011 6:09:42 pm It seems like the eZHTTPTool::parseHTTPResponse doesn't parse the body of response that has "Transfer-Encoding: chunked" header. Actually the body is left as it is and the chunks are not concatenated together in one piece. So, is this wanted behaviour? If it is, then it would be nice to add a method that parses the chunks and gives back the body in one piece... (or is there already such a function?) -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Brandon Chambers	Tuesday 07 June 2011 3:22:38 pm Seems like it's intended, I guess it depends on what the content/type headers say. It gives the user more power to implement it how they see fit. A downside is a lack of support for different types of content. But is it worth it for eZ Systems to implement a bunch of different handlers per content type? Probably not. I found a few references of its use in the kernel as well as the class definition in doxygen. [ezroot]/kernel/setup/steps/ezstep_site_types.php [ezroot]/kernel/shop/classes/exchangeratehandlers/ezecb/ezecbhandler.php I didn't see any issues (open nor resolved) for parseHTTPResponse that pertain to your question either. Brandon Chambers brandon@granitehorizon.com blog: http://blog.divdesigns.com Granite Horizon / http://granitehorizon.com

Author

Message

Monday 06 June 2011 6:09:42 pm

It seems like the eZHTTPTool::parseHTTPResponse doesn't parse the body of response that has "Transfer-Encoding: chunked" header. Actually the body is left as it is and the chunks are not concatenated together in one piece.

So, is this wanted behaviour?

If it is, then it would be nice to add a method that parses the chunks and gives back the body in one piece...

(or is there already such a function?)

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Brandon Chambers

Tuesday 07 June 2011 3:22:38 pm

Seems like it's intended, I guess it depends on what the content/type headers say. It gives the user more power to implement it how they see fit. A downside is a lack of support for different types of content. But is it worth it for eZ Systems to implement a bunch of different handlers per content type? Probably not.

I found a few references of its use in the kernel as well as the class definition in doxygen.

[ezroot]/kernel/setup/steps/ezstep_site_types.php

[ezroot]/kernel/shop/classes/exchangeratehandlers/ezecb/ezecbhandler.php

I didn't see any issues (open nor resolved) for parseHTTPResponse that pertain to your question either.

Brandon Chambers
brandon@granitehorizon.com
blog: http://blog.divdesigns.com
Granite Horizon / http://granitehorizon.com

eZ debug

Timing:	Jan 29 2025 23:49:15
Script start
Timing:	Jan 29 2025 23:49:15
Module start 'layout'
Timing:	Jan 29 2025 23:49:15
Module start 'content'
Timing:	Jan 29 2025 23:49:15
Module end 'content'
Timing:	Jan 29 2025 23:49:15
Script end

Main resources:

Total runtime	0.0171 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.3906	151.2422
Module start 'layout'	0.0048	0.0024	739.6328	36.7188
Module start 'content'	0.0072	0.0083	776.3516	90.1406
Module end 'content'	0.0155	0.0015	866.4922	29.9766
Script end	0.0171		896.4688

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	13.4599	14	0.0002
Check MTime	0.0010	5.9106	14	0.0001
Mysql Total
Database connection	0.0008	4.7151	1	0.0008
Mysqli_queries	0.0023	13.4835	3	0.0008
Looping result	0.0000	0.0711	1	0.0000
Template Total	0.0011	6.7	1	0.0011
Template load	0.0008	4.8670	1	0.0008
Template processing	0.0003	1.8169	1	0.0003
Override
Cache load	0.0005	3.1560	1	0.0005
General
dbfile	0.0034	19.8679	8	0.0004
String conversion	0.0000	0.0404	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs