1209537 - Home controller loads /about/home and /favicon.ico on launch

Status: NEW

(Firefox for iOS :: General, defect)

Description

[Richard Newman [:rnewman]]

[DEBUG] Did open connection on socket 16
[DEBUG] Connection received 378 bytes on socket 16
[DEBUG] Connection aborted with status code 405 on socket 16
[DEBUG] Connection sent 113 bytes on socket 16
[DEBUG] Did close connection on socket 16
[VERBOSE] [::1:6571] ::1:53854 405 "GET /about/home/" (378 | 113)

[DEBUG] Did open connection on socket 21
[DEBUG] Connection received 302 bytes on socket 21
[DEBUG] Connection aborted with status code 405 on socket 21
[DEBUG] Connection sent 113 bytes on socket 21
[DEBUG] Did close connection on socket 21
[VERBOSE] [::1:6571] ::1:53855 405 "GET /favicon.ico" (302 | 113)


This is ridiculous. They both 405, but we make and handle the requests!

Comment 1

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

I think this is by design. /about/home is actually mapped to a web server handler that returns a 200 with an empty body.

Brian, any thoughts?

Comment 2

[Brian Nicholson (:bnicholson)]

I'm not sure what the performance implications are of trying to fetch a resource on our client server. Might be negligible, but would be nice to clean up anyway. A few ideas:

* Hardcode an exception for localhost or about pages so that we don't try to fetch favicons for these URLs.
* Put an actual favicon in the place where the server is checking. It will try (and succeed) the first time, then use the cached favicon for all future home visits.
* Continue returning an HTTP error, but make our favicon cache smarter by recording failures so that we don't retry on every visit.

With options 2 and 3, we could also consider preloading the cache to prevent the first-run hit. But again, I'm not sure how much effort is worth spending to optimize this.