[Idea] Show error on 403 or 404 for /wiki
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- full-stack
Research direction
Start by reproducing the /wiki requests for a user without read access and for a nonexistent wiki in the supported browsers. Trace the server handling for those 403 and 404 responses; done means each returns a page with a specific error message and a “go back home” button instead of an empty or browser-generated page.
Written by the indexing model from the issue text.
Description
If the user has no read access for a wiki, the server responds with an empty 403 page.
If the wiki does not exist, the server responds with an empty 404 page.
PC firefox gives a blank page.
Mobile firefox gives
Cannot Complete Request
Additional information about this problem or error is currently unavailable.
Mobile chrome gives a little more info.
The server should handle the issue by giving a page with a specific error message and a "go back home" button instead of letting the browser handle it.
- Dominant language
- TypeScript
- Stars
- 60
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 TiddlyWiki/MultiWikiServer
-
Difficulty 3/5 1-3 hours Newbie friendliness 15/100
TiddlyWiki/MultiWikiServer#141 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
TiddlyWiki/MultiWikiServer#140 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#139 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#138 ·
-
User creation fails with 500 error when email field is left blank - missing frontend validationOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#136 · 1 reaction ·
All issues in TiddlyWiki/MultiWikiServer
Similar issues
-
Create/import wallet form shows raw "password must be at least 1 characters" instead of the translated messagePossibly taken @CapThunder19 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
joinmarket-webui/jam#1538 ·
Maintainers usually reply within 1 day
-
t0ggles
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nolimits4web/swiper#8240 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/inspector#2723 ·
Maintainers usually reply within 1 day
-
status:approved type:bug
Difficulty 1/5 Under an hour Newbie friendliness 70/100
egdev6/quorb#109 · 1 comment ·
Maintainers usually reply within 1 day