All geek questions in one place

HTTP compression - is it possible to configure the client to compress data sent to the server?

I am using IIS 7 as a web server for my application. If I turn on dynamic compression of content on the server, will it also allow clients to send compressed data to the server, if they can?

I mean, my application uses SOAP web services, and clients usually send large chunks of data to the server. Clients are written in C # /. NET Is there any configuration that I can do in the link to the / serice web link to tell them to compress the content before sending it to IIS? And do I need to do any configuration in IIS for this to work?

Thanks in advance

+3
source share
1 answer

HTTP compression works as a client defining a header Accept-Encodingwith the types of compression it accepts:

Accept-Encoding: compress, gzip

The server then sees this and will choose one of the encoding types based on the accept encoding rules defined here . The answer will be in one of the accepted values ​​or in the encoding of identification.

Requests:

In general, a request cannot be compressed first because the message begins with the request. An HTTP client could send a request for parameters, although using this, if you have control over the source code of the client and server, you can do this.

OPTIONS , /, Request-URI. / , , , .

apache SVN, svn. HTTP .

. RFC 2616: 9

+7

Source: https://habr.com/ru/post/1741495/

More articles:


All Articles