If you look at your times http has bigger waiting time and smaller receiving time. https on the other hand has smaller waiting time and bigger receiving time. I would interpret this as the http port on the shared hosting server is more busy, thus a request stays longer in the queue until is accepted … Read more
What about this one ? When requesting the login form which is a public page, you get what you want, so it’s a 200 status code : GET /login -> 200 When requesting for a page that needs a http level authentication that you didn’t initiated (basic http, ssl certificate, etc.), the application must tell … Read more
I’ve tested it, with a home-made server and a simple response. Not sure if the response is well-formed because no browser understands it 100% OK. But here are the results: Firefox 67.0.1 (64-bit): Renders only the last part, others are ignored. IE 11.503: Saves all the content in a single file (including the boundaries), nothing … Read more
It’s actually super easy… I’m sure you can just show a UIAlertView when the auth challenge delegate is shown (or prior to loading the URL, if you know for sure that the URL you’re hitting will prompt for auth login info). Anyways, the trick is to create your own NSURLConnection and I do some logic … Read more
The only advantage of POST-creation over PUT-creation is the server generation of IDs. I don’t think it worths the lack of idempotency (and then the need for removing duplicates or empty objets). Instead, I would use a PUT with a UUID in the URL. Owing to UUID generators you are nearly sure that the ID … Read more
REST is a design style for protocols, it was developed by Roy Fielding in his PhD dissertation and formalised the approach behind HTTP/1.0, finding what worked well with it, and then using this more structured understanding of it to influence the design of HTTP/1.1. So, while it was after-the-fact in a lot of ways, REST … Read more
Based on your response, the answer to your question is to create a new resource that contains that single set of information. e.g. GET /Customer/1212/RecentPurchases Creating composite urls that have many identifiers in a single url limits the benefits of caches and adds unnecessary complexity to the server and client. When you load a web … Read more
From HTTP Header Field Definitions: 14.9.3 Modifications of the Basic Expiration Mechanism … s-maxage If a response includes an s-maxage directive, then for a shared cache (but not for a private cache), the maximum age specified by this directive overrides the maximum age specified by either the max-age directive or the Expires header. … Note, … Read more
Actually a fair amount of people use PUT and DELETE, mostly for non-browser APIs. Some examples are the Atom Publishing Protocol and the Google Data APIs: http://www.ietf.org/rfc/rfc5023.txt http://code.google.com/apis/gdata/docs/2.0/basics.html Beyond that, you don’t see PUT/DELETE in common usage because most browsers don’t support PUT and DELETE through Forms. HTML5 seems to be fixing this: http://www.w3.org/TR/html5/forms.html#form-submission-0 The … Read more
Pretty old post but I really want to bring some light into the darkness. The answer itself is quite simple. DR;TL Variables in NGINX are always global and once defined accessable from anywhere in the configuration. Therefore it would not make any sense to define a map in a server or location block. map creates … Read more