http-headers

问题 I am currently writing a HTTP client to do a HTTP POST on a URL that returns a HTTP response. However, for error messages code 400 and 500, it sends back non chunked HTTP response, and for success messages, 201, it sends a chunked response. In the request, I am setting the content-length, so I am not sure why it is still sending us the chunked transfer encoding. Is there any other header I can set in the request, that will tell the HTTP server not to send chunked encoding? headerList.append(

问题 I was wondering if the order of the actual languages in the Accept-language matters. For example, if our HTTP GET message contained the header: Accept-Language: en-us, en-gb;q=0.2, en;q=0.3, fr, fr-ch, da, fi ...would the browser prefer Traditional French (fr) over Swiss French (fr-ch) even though they both have no Relative Quality Factor q mentioned, and hence would be 1. 回答1: No, the ordering does not matter. 回答2: When I implemented this, I used a stable sort so that values with the same

问题 Should the HEAD and GET methods return the same status code? More specifically, we have run into the situation where a client website is returning a 200 when we do a HEAD , but returns a 303 when we do a GET . It has to do with redirecting to a language specific page based on location, but shouldn't the HEAD then also ask you to redirect? 回答1: but shouldn't the HEAD then also ask you to redirect? The key is the word SHOULD . From the HTTP method specification, RFC2616: 9.4 HEAD The HEAD

问题 I am trying to get data from web services from my app to load a list and to load more on scroll using pull refresh & ListPaging plugins. I tried this with flickr API and it works fine, but problem comes when I try to access our own services because they expect "Authorization" header with Base64 encoded data and "Accept" header to decide format of response. This is how I have defined my store: Ext.define('myshop.store.CatalogListStore',{ extend:'Ext.data.Store', requires: [ 'myshop.model

问题 According to RFC 2616, generation of entity tags by HTTP servers is optional. However, I couldn't find what a conditionally compliant HTTP server should do if it receives an If-Match (or If-None-Match ) header. Should it just ignore those headers or should it respond with 412 Precondition Failed ? UPD: Just to clarify, I'm assuming that the server in question does not support entity tags. 回答1: While the RFC2616 is implicit on the matter, you can deduce from, say 14.26 (If-None-Match), that if

问题 I am working on a website on my localhost and suddenly I'm now getting this errors. I get this error on Firefox <script> source URI is not allowed in this document And nothing on chrome,` but if I try using the files code, I get: Application Error: There was a problem getting data for the application you requested. The application may not be valid, or there may be a temporary glitch. Please try again later. It is basically for: https://connect.facebook.net/en_US/sdk.js. The browser doesn't

问题 I'm trying to get some datas from an external API (from Mashape) that requires a specific header to set the API key. Everything is ok using jQuery : $.ajax({ url: 'https://omgvamp-hearthstone-v1.p.mashape.com/cardbacks', type: 'GET', data: {}, dataType: 'json', success: function(data) { console.dir((data.source)); }, error: function(err) { alert(err); }, beforeSend: function(xhr) { xhr.setRequestHeader("X-Mashape-Authorization", "MY_API_KEY"); } }); However, when I'm trying to do the same

问题 Is it possible to read the Browser(Client machine) time when a request is made to the servlet? 回答1: I don't believe so. Unfortunately the HTTP Date header is only sent for PUT or POST messages, and even then it's optional: Clients SHOULD only send a Date header field in messages that include an entity-body, as in the case of the PUT and POST requests, and even then it is optional. A client without a clock MUST NOT send a Date header field in a request. If you have control of the client, you

问题 Is this valid and correct? RewriteRule ^myOldPage.html$ /index.php#info [R] I'm specifically interested about the #info part. 回答1: Yes. That's a valid 301 redirect (the HTTP standard allows for any valid URI to be provided as the redirect). Now the caveat: Not all search engines may love the redirect. Google does a fantastic job of handling anchor tags (they even have a patent on this), while others will completely ignore them. As long as that's not an issue, the redirect is technically valid

问题 I have an AWS Elastic Beanstalk (Node.js) setup behind an Elastic Load Balancer and alerts setup for the load balancer. Each night I get tons of alerts for: Environment health has transitioned from Ok to Severe. 100.0 % of the requests are erroring with HTTP 4xx. This is due to trawls of different PHP hackz and phpmyadmin, dbadmin, etc. using the HEAD method in 99% of the cases. Since we have an external AIM service they trigger on these alerts as well creating an issue for each (which we now