It's very likely that Chrome saw that non-secured, GET-based resource, and decided to grab it to see if it is interesting. It does this, which is why it is so darned fast. It is also explicitly permitted to do this.
PROTIP: Never, ever,
ever use a HTTP GET request to
do something.
Or,
put another way,
Quote:
There are four basic methods in HTTP: GET, POST, PUT, and DELETE. GET is used most of the time. It is used for anything that's safe, that doesn't cause any side effects. GET is able to be bookmarked, cached, linked to, passed through a proxy server. It is a very powerful operation, a very useful operation.
POST by contrast is perhaps the most powerful operation. It can do anything. There are no limits as to what can happen, and as a result, you have to be very careful with it. You don't bookmark it. You don't cache it. You don't pre-fetch it. You don't do anything with a POST without asking the user. Do you want to do this? If the user presses the button, you can POST some content. But you're not going to look at all the buttons on a page, and start randomly pressing them. By contrast browsers might look at all the links on the page and pre-fetch them, or pre-fetch the ones they think are most likely to be followed next. And in fact some browsers and Firefox extensions and various other tools have tried to do that at one point or another.
_________________
Code:
/* TODO: need to add signature to posts */
FAQ
Search
Members
Register
Login [ Anonymous ]
