CODEWITHSUNDEEP
javascriptasp.netgetrequestgzip
MANISHDAN LANGA
MANISHDAN LANGA

Reputation: 2237

ajax send request with encoding gzip is not working

Ajax send request with encoding gzip (iis7) is not working below are the code for send request can some one help me what is wrong in my code.

Thanks in advance

function sendRequest(url, callback, postData)
{
   var req = createXMLHTTPObject();
   if (!req) {
      return;
   }

   var method = (postData) ? "POST" : "GET";
   req.open(method, "xml/" + url, true);
   req.setRequestHeader('User-Agent', 'XMLHTTP/1.0');

   if (postData) {
      req.setRequestHeader('Content-type', 'application/x-www-form-urlencoded');
      req.setRequestHeader("Content-Encoding", "gzip");

   }

   req.onreadystatechange = function() {

   }

   req.send(postData);
}

Upvotes: 3

Views: 15337

Answers (3)

robocat
robocat

Reputation: 5443

One way to transparently have the requests for your XMLHttpRequest highly compressed is to use HTTP/2 (e.g. serve your website via CloudFlare).

When using HTTP/2, then although the HTTP headers do not say Content-Encoding: gzip the underlying HTTP/2 protocol compresses everything.

It also compresses much better than gzip because:

  • it compresses headers
  • header compression uses a standard dictionary
  • I think data compression builds a dictionary over multiple messages (brotli - I haven't double-checked that though)

You can see if your server is using HTTP/2 by:

  1. Open Chrome, and F12 to open developer tools
  2. Click on the network tab
  3. close the request inspector panel (has tabs Headers Preview Response Timing)
  4. Right click on the Name header of the list of requests and tick Protocol
  5. Navigate to your website and watch what protocol is used for all requests - in the protocol column you want to see h2 not http/1.1

Example log of HTTP/2 network requests withn Chrome developer tools

I wouldn't recommend using JavaScript compression libraries because that causes slowdown and inefficiencies.

Upvotes: 2

Denys Séguret
Denys Séguret

Reputation: 382464

The problem doesn't seem to be related to header but to compression.

You don't seem to compress your postData.

If postData is already compressed, no need to try to manually set content-encoding.

If it is not, either let the browser negotiate the transfer encoding with the server (this is part of the protocol and done automatically, the server saying if it accepts it, but I think that's rarely the case) or (if you really really need to) encode it yourself. This SO question indicates a library to compress browserside : JavaScript implementation of Gzip

Upvotes: 1

tuoxie007
tuoxie007

Reputation: 1236

Considering the security, browser does not allow you to override some headers including "Content-Encoding".

Upvotes: 5

Related Questions