Bug: Campus deployment on server shows GET requests
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing POST requests to /api/v1/timetable/ and /api/v1/timetable, then compare the campus server logs and methodNotAllowed response. Trace the timetable route registration and request handling; done means the trailing-slash request is handled as the expected POST without producing a methodNotAllowed error.
Written by the indexing model from the issue text.
Description
/api/v1/timetable/ route shows up as GET in campus server logs and causes a methodNotAllowed error, while api/v1/timetable without the trailing slash shows up as a POST, which is expected behavior.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nyjc-computing/campus-api-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
nyjc-computing/campus-api-python#2 · 1 assignee ·
All issues in nyjc-computing/campus-api-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100