server socket receives 2 http requests when I send from chrome and receives one when I send from firefox

by

I had a similar issue with my node server. It is due to the following bug in Chrome. In summary, Chrome is sending a request for a favicon on every request. As, is likely, you aren’t sending a favicon back, it requests one after every legitimate request.

Firefox, and most other browsers, also send out a request for a favicon when they first connect, but cache the result i.e. if there isn’t a favicon returned first time, they don’t keep trying – which is why you’re only seeing a single request from Firefox. It seems Chrome is unfortunately a little too persistent with its favicon requestiness.

More Related Contents:

  1. how can an application use port 80/HTTP without conflicting with browsers?
  2. Uses of content-disposition in an HTTP response header
  3. What’s the difference between a POST and a PUT HTTP REQUEST?
  4. Differ between header and content of http server response (sockets)
  5. How to detect server-side whether cookies are disabled
  6. ‘Refresh’ HTTP header
  7. Why is it common to put CSRF prevention tokens in cookies?
  8. Which status code should I use for failed validations or invalid duplicates?
  9. Easy HTTP requests with gzip/deflate compression
  10. CORS request with Preflight and redirect: disallowed. Workarounds?
  11. How to redirect user’s browser URL to a different page in Nodejs?
  12. Why does my web server software disallow PUT and DELETE requests?
  13. What does “pending” mean for request in Chrome Developer Window?
  14. Difference between HTTP redirect codes
  15. How to make an HTTP get request in C without libcurl?
  16. Chrome hangs after certain amount of data transfered – waiting for available socket
  17. Using “transfer-encoding: chunked”, how much data must be sent before browsers start rendering it?
  18. What is a full specification of X-Forwarded-Proto HTTP header?
  19. Do web browsers always send a trailing slash after a domain name?
  20. What exactly is an HTTP Entity?
  21. Payloads of HTTP Request Methods
  22. What HTTP response headers are required
  23. Chunked transfer encoding – browser behavior
  24. Is it acceptable for a server to send a HTTP response before the entire request has been received?
  25. Domain set cookie for subdomain
  26. What does HTTP/1.1 302 mean exactly?
  27. Chunked encoding and content-length header
  28. Is a URL with // in the path-section valid?
  29. What is a connection timeout during a http request
  30. How to set up CORS or OPTIONS for Rocket.rs

Leave a Comment