![]() This enables a client to indicate its willingness to receive a particular encoding in this header. ![]() Encoding of HTTP responsesĬontent encoding of HTTP responses is negotiated using the Accept-Encoding HTTP request header. You can configure these settings globally, per remote host, or per listening interface. In Policy Studio, an Input Encodings list specifies the content encodings that the API Gateway can accept from peers, and an Output Encodings list specifies the content encodings that the API Gateway can apply to outgoing messages. A client that takes six seconds to download an uncompressed XML file might only take two seconds for a compressed version of the same file. Compressing files causes a slightly higher load on the server, but this is compensated by a significant decrease in client connection times to the server. ![]() This enables the API Gateway to compress files and deliver them to clients (for example, web browsers) and to back-end servers.įor example, HTML, text, and XML files can be compressed to approximately 20% to 30% of their original size, thereby saving on server traffic. The API Gateway supports HTTP content encoding for the gzip and deflate compressed content encodings. ![]() Configure input and output content encodings globally, per remote host, or per listening interface.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |