GET on app cap can return 304 instead of new launch link
Bug #814813 reported by
Chris Osborn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Sitelier Kernel |
Fix Committed
|
High
|
Seth Purcell | ||
Bug Description
Depending on cache headers, the kernel will sometimes return a 304 (not modified) status for a GET request to an app capability, rather than a 303 redirect with a launch link. This results in the user reconnecting to an existing app session if one exists, or failure to launch otherwise.
Related branches
| Changed in sitelier-kernel: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Seth Purcell (seth-purcell) |
| Changed in sitelier-kernel: | |
| status: | Confirmed → In Progress |
| Changed in sitelier-kernel: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
