snapd unexpected HTTP status code 403

Bug #2039337 reported by Birgit Edel
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
Fix Released
William Grant

Bug Description

snapd 2.60.3 (log emitted prior to retrieving that version) still claims not expecting what the store keeps doing:

snapd.service snapd[1300]: stateengine.go:149: state ensure error: cannot decode new commands catalog: got unexpected HTTP status code 403 via GET to ""

Maybe the server could signal many different, but all expected status (e.g. 429, 503, 529) thus allowing the client to add client-version-dependent pointers to the error message:
* this is temporary, will retry after [interval]
* this is server-side, check
* this is you exceeding a rate limit, see LP: #1710022

This forum post appears to hint at a fix in that direction being live:

see also LP: #1950156

Revision history for this message
William Grant (wgrant) wrote :

We usually return 429 in the names ratelimiting situation, but had missed one case which was still a 403. That's fixed now -- reply here if you see something like that again!

Changed in snapstore-server:
assignee: nobody → William Grant (wgrant)
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.