RejectedSoftware Forums

Sign up

requestHTTP with gzip

avatar
Sebastiaan Koppe
Posted Mon, 08 Aug 2016 19:59:53 GMT
Reply

I am hitting some limits of plain text transfer and would like to gzip it. Any possibility of using the GzipOutputStream with requestHTTP?

If not implemented yet, I was thinking about using a similar method like in the HTTPClientResponse. There the OutputStream type for the bodyReader gets determined by some headers (chunked, gzip, limited, etc.).

For the HTTPClientRequest it would then work like this: if you would set the appropriate gzip header before calling the bodyReader, it would then be instantiated with a GzipOutputStream upon calling the bodyReader property.

How 'bout that?

Re: requestHTTP with gzip

avatar
Sebastiaan Koppe
Posted Mon, 08 Aug 2016 20:01:30 GMT in reply to Sebastiaan Koppe
Reply

On Mon, 08 Aug 2016 19:59:53 GMT, Sebastiaan Koppe wrote:

I am hitting some limits of plain text transfer and would like to gzip it. Any possibility of using the GzipOutputStream with requestHTTP?

If not implemented yet, I was thinking about using a similar method like in the HTTPClientResponse. There the OutputStream type for the bodyReader gets determined by some headers (chunked, gzip, limited, etc.).

For the HTTPClientRequest it would then work like this: if you would set the appropriate gzip header before calling the bodyReader, it would then be instantiated with a GzipOutputStream upon calling the bodyReader property.

How 'bout that?

Apparently I posted on github as well...

https://github.com/rejectedsoftware/vibe.d/issues/1544

Re: requestHTTP with gzip

avatar
Sebastiaan Koppe
Posted Sun, 14 Aug 2016 13:55:45 GMT in reply to Sebastiaan Koppe
Reply

On Mon, 08 Aug 2016 19:59:53 GMT, Sebastiaan Koppe wrote:

I am hitting some limits of plain text transfer and would like to gzip it. Any possibility of using the GzipOutputStream with requestHTTP?

If not implemented yet, I was thinking about using a similar method like in the HTTPClientResponse. There the OutputStream type for the bodyReader gets determined by some headers (chunked, gzip, limited, etc.).

For the HTTPClientRequest it would then work like this: if you would set the appropriate gzip header before calling the bodyReader, it would then be instantiated with a GzipOutputStream upon calling the bodyReader property.

How 'bout that?

It doesn't make sense. It was obvious it won'the work but took me some time to realise:)