http-get

问题 I want to be able to create a custom AngularJS service that makes an HTTP \'Get\' request when its data object is empty and populates the data object on success. The next time a call is made to this service, I would like to bypass the overhead of making the HTTP request again and instead return the cached data object. Is this possible? 回答1: Angular's $http has a cache built in. According to the docs: cache – {boolean|Object} – A boolean value or object created with $cacheFactory to enable or

问题 This question already has an answer here: maximum length of HTTP GET request? 7 answers Is there a limit to the length of a GET request? 回答1: Not in the RFC, no, but there are practical limits. The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too

问题 This question already has answers here : Is an HTTPS query string secure? (9 answers) Closed 8 months ago . Do querystring parameters get encrypted in HTTPS when sent with a request? 回答1: Yes. The querystring is also encrypted with SSL. Nevertheless, as this article shows, it isn't a good idea to put sensitive information in the URL. For example: URLs are stored in web server logs - typically the whole URL of each request is stored in a server log. This means that any sensitive data in the

问题 <script src=\"http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.js\" type=\"text/javascript\"></script> <script> $.get(\"http://example.com/\", function(data) { alert(data); }); </script> it does an OPTIONS request to that URL, and then the callback is never called with anything. When it isn\'t cross domain, it works fine. Shouldn\'t jQuery just make the call with a <script> node and then do the callback when its loaded? I understand that I won\'t be able to get the result (since it is

问题 From what I can gather, there are three categories: Never use GET and use POST Never use POST and use GET It doesn\'t matter which one you use. Am I correct in assuming those three cases? If so, what are some examples from each case? 回答1: Use POST for destructive actions such as creation (I'm aware of the irony), editing, and deletion, because you can't hit a POST action in the address bar of your browser. Use GET when it's safe to allow a person to call an action. So a URL like: http:/

问题 I\'m developing a new RESTful webservice for our application. When doing a GET on certain entities, clients can request the contents of the entity. If they want to add some parameters (for example sorting a list) they can add these parameters in the query string. Alternatively I want people to be able to specify these parameters in the request body. HTTP/1.1 does not seem to explicitly forbid this. This will allow them to specify more information, might make it easier to specify complex XML