Closed
Bug 1037236
Opened 10 years ago
Closed 10 years ago
Unable to access an unpublished packaged app using the direct link
Categories
(Marketplace Graveyard :: Consumer Pages, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: krupa.mozbugs, Unassigned)
References
()
Details
Attachments
(1 file)
1.51 MB,
image/png
|
Details |
steps to reproduce:
1. Load https://marketplace-dev.allizom.org/developers/app/test-webapi-permissions-10/status
2. Click on the direct link listed to access the details page
expected behavior:
link loads since the app is approved but unpublished
observed behavior:
link returns a 404
Comment 1•10 years ago
|
||
WFM now. I think it could be fireplace caching? Next time check the status code of the API call?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 2•10 years ago
|
||
(In reply to Rob Hudson [:robhudson] from comment #1)
> WFM now. I think it could be fireplace caching? Next time check the status
> code of the API call?
Fireplace caches the response only once and we update the cache asynchronously when we use the cached version. So if you refresh the page once, we use the updated API response. You can check in your Network tab to see the XHR that was used.
Comment 3•10 years ago
|
||
(In reply to Christopher Van Wiemeersch [:cvan] from comment #2)
> (In reply to Rob Hudson [:robhudson] from comment #1)
> > WFM now. I think it could be fireplace caching? Next time check the status
> > code of the API call?
>
> Fireplace caches the response only once and we update the cache
> asynchronously when we use the cached version. So if you refresh the page
> once, we use the updated API response. You can check in your Network tab to
> see the XHR that was used.
Where is the code that does this? Does it do this for non-200 responses?
Comment 4•10 years ago
|
||
(In reply to Rob Hudson [:robhudson] from comment #3)
> (In reply to Christopher Van Wiemeersch [:cvan] from comment #2)
> > (In reply to Rob Hudson [:robhudson] from comment #1)
> > > WFM now. I think it could be fireplace caching? Next time check the status
> > > code of the API call?
> >
> > Fireplace caches the response only once and we update the cache
> > asynchronously when we use the cached version. So if you refresh the page
> > once, we use the updated API response. You can check in your Network tab to
> > see the XHR that was used.
>
> Where is the code that does this? Does it do this for non-200 responses?
https://github.com/mozilla/fireplace/commit/51c372a#diff-c7f67bebbc3c25b4f410586f52308faaR141
You need to log in
before you can comment on or make changes to this bug.
Description
•