View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000408 | BiQubic Framework | API | public | 2020-01-02 09:45 | 2020-01-21 16:24 |
Reporter | BootBlock | Assigned To | BootBlock | ||
Priority | urgent | Severity | block | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0000408: Can't submit exceptions | ||||
Description | This has happened before and I thought I fixed it, but it's happening now either way. Sending an exception report results in the tracker giving a 403 Forbidden error when trying to list projects. The textual description is:
If I remember, the submitter is using the wrong user? Maybe Anonymous? | ||||
Tags | BiQubic.Framework | ||||
|
I've added a specific catch for the user rights issue that notifies the user about the problem, just in case it happens again in the future on a user's machine. Still haven't (re)discovered the issue, though... |
|
Alright, fixed. Turns out updating MantisBT broke a change I had to make to get authorisation working as it seems the Authorization header isn't be preserved when using the REST API. For future reference: 1) Open At the time of writing, the .htaccess for MantisBT 2.23.0 should entirely consist of the following (note the addition of the first line):
|
Date Modified | Username | Field | Change |
---|---|---|---|
2020-01-02 09:45 | BootBlock | New Issue | |
2020-01-02 09:45 | BootBlock | Assigned To | => BootBlock |
2020-01-02 09:45 | BootBlock | Tag Attached: BiQubic.Framework | |
2020-01-02 09:56 | BootBlock | Note Added: 0000137 | |
2020-01-02 11:01 | BootBlock | Note Added: 0000138 | |
2020-01-02 11:01 | BootBlock | Note Edited: 0000138 | |
2020-01-02 11:01 | BootBlock | Note Edited: 0000138 | |
2020-01-02 11:03 | BootBlock | Note Edited: 0000138 | |
2020-01-02 11:03 | BootBlock | Note Edited: 0000138 | |
2020-01-02 11:04 | BootBlock | Status | new => resolved |
2020-01-02 11:04 | BootBlock | Resolution | open => fixed |
2020-01-21 16:24 | BootBlock | Status | resolved => closed |