Note that there are some explanatory texts on larger screens.

plurals
  1. POHttp request header "Accept-Charset" is not recognized
    text
    copied!<p>I am trying to make a REST call using chrome DHC and Advanced rest clients. For example:</p> <p>A HEAD call to <a href="http://www.google.co.in" rel="nofollow">http://www.google.co.in</a> using advanced REST client gives:</p> <pre><code>Redirect To:https://www.google.co.in/ with status: 302 Show explanation HTTP/1.1 302 Found Redirection information has not been cached. Location: https://www.google.co.in/ Cache-Control: private Content-Type: text/html; charset=UTF-8 Date: Fri, 29 Nov 2013 06:57:46 GMT Server: gws X-XSS-Protection: 1; mode=block X-Frame-Options: SAMEORIGIN Alternate-Protocol: 80:quic Content-Length: 222 Proxy-Connection: Keep-Alive Connection: Keep-Alive Status 200 OK Show explanation Loading time: 764 Request headers Accept: application/json Accept-Language: en-US User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 X-Chrome-Variations: &lt;some value&gt; Accept-Encoding: gzip,deflate,sdch Cookie: &lt;some value&gt; Response headers status: 200 OK version: HTTP/1.1 alternate-protocol: 443:quic cache-control: private, max-age=0 content-encoding: gzip content-length: 34821 content-type: text/html; charset=UTF-8 date: Fri, 29 Nov 2013 06:57:46 GMT expires: -1 server: gws x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block </code></pre> <p>I am more interested on details of request header as <strong>"Accept-Charset"</strong> is not recognized. If i give anything as header it is atleast displayed in request header. Now some questions:</p> <ol> <li><p>why this is not recognized? is this client problem or server problem? do i need to use any other client. I am not aware.</p></li> <li><p>If it is recognized then I should be able to validate this value in server code, which in my case is running in jetty?</p></li> </ol> <p>Thanks, Akhi</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload