Closed Bug 1960833 Opened 1 month ago Closed 7 days ago

Suggestion Network Traffic Performance telemtrety cached requests management

Categories

(Firefox :: Search, enhancement)

Firefox 138
Desktop
All
enhancement

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox137 --- unaffected
firefox138 --- unaffected

People

(Reporter: aflorinescu, Unassigned)

References

Details

Following the traffic when suggestions api is triggered for various engines, the following categories have been observed:

1. No cache

  • google.com: no cached (304) suggestion requests
  • duckduckgo.com: no cached (304) suggestion requests
  • ebay.com: no cached (304) suggestion requests
  • ecosia.org no cached (304) suggestions requests
  • seznam.cz no cached (304) suggestions requests
  • naver-kr no cached (304) suggestions requests
  • salidzini.lv no cached (304) suggestions requests

2. Cached requests

  • qwant.com: cached (304) suggestion requests

3. Cached, but status returned is 200

  • en.wikipedia.com: cached transfer, status is still 200
  • bing.com: cached transfer, status is still 200
  • LEO Eng-Deu cached, but with status 200

Note:

  • daum-kr unknown if cached requests - suggestions api seems to be either slow or malfunctioning - in the sense that there seems to be something like ~50% suggestions api aborting, immediately after a 200, I can see 1 or 2 aborts, regardless if triggering the same keyword suggestion or just typing normally

Chris will reach to you to figure out the next steps here.

Flags: needinfo?(cbellini)

For the foreseeable future, we won't have an urgent need to resolve the cached requests from Qwant.

Status: NEW → RESOLVED
Closed: 7 days ago
Flags: needinfo?(cbellini)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.