Plume/Plume
9
18
Fork 24
Code Issues 177 Pull requests 8 Releases 8 Wiki Activity

Special character '/' allowed in article title causes 404 #1111

New issue
Open
opened 2022-08-21 21:30:30 +00:00 by freyja_wildes · 3 comments
freyja_wildes commented 2022-08-21 21:30:30 +00:00
Copy link

I have this article on my instance that return a 404. The article is listed on the main page, on the page for the blog it's published under with proper title, summary and other infos. The author of the article can't edit it or "do anything with it".
I also checked using a Mastodon account, the post for the article does appear on the profile of the author with the link.
Link to the article in question: existing article returning 404
The article is written in French.

For the technical aspect of it:
I've checked the data base, the article is listed there, it has sources.
My Plume instance was deployed using Ansible (the Python tool) and use a custom Systemd unit file to run. I've looked at the journal for that unit, not much to say regarding the logs. Here is an excerpt of it:

-- Logs begin at Sun 2022-08-21 11:06:10 CEST, end at Sun 2022-08-21 22:35:39 CEST. --
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.284332Z  INFO _: Outcome: Success
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.284454Z  INFO _: Response succeeded.
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294360Z  INFO rocket::rocket: GET /static/cached/740aac32/css/default-light/fonts/Vazir_WOL/Vazir_WOL.css text/css:
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294409Z  INFO _: Matched: GET /static/cached/<_build_id>/css/<file..> (theme_files)
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294501Z  INFO _: Outcome: Success
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294603Z  INFO _: Response succeeded.
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.301729Z  INFO rocket::rocket: GET /static/cached/740aac32/css/default-light/fonts/Shabnam_WOL/Shabnam_WOL.css text/css:
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.301832Z  INFO _: Matched: GET /static/cached/<_build_id>/css/<file..> (theme_files)
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.301926Z  INFO _: Outcome: Success
août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.302026Z  INFO _: Response succeeded.

So if I get things right, Rocket is finding the route to the article. Or am I missing something?

Any idea what could have went wrong? Do you think there might be a solution I could apply to fix the situation?

I have this article on my instance that return a 404. The article is listed on the main page, on the page for the blog it's published under with proper title, summary and other infos. The author of the article can't edit it or "do anything with it". I also checked using a Mastodon account, the post for the article does appear on the profile of the author with the link. Link to the article in question: [existing article returning 404](https://blog.witch.academy/~/Sant%C3%A9MentaleDunBlobChaotique/Un%20s%C3%A9jour%20hospitalier%20bipolaire%202%20avec%20TDI%2FATDS*) The article is written in French. For the technical aspect of it: I've checked the data base, the article is listed there, it has sources. My Plume instance was deployed using Ansible (the Python tool) and use a custom Systemd unit file to run. I've looked at the journal for that unit, not much to say regarding the logs. Here is an excerpt of it: ``` -- Logs begin at Sun 2022-08-21 11:06:10 CEST, end at Sun 2022-08-21 22:35:39 CEST. -- août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.284332Z INFO _: Outcome: Success août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.284454Z INFO _: Response succeeded. août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294360Z INFO rocket::rocket: GET /static/cached/740aac32/css/default-light/fonts/Vazir_WOL/Vazir_WOL.css text/css: août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294409Z INFO _: Matched: GET /static/cached/<_build_id>/css/<file..> (theme_files) août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294501Z INFO _: Outcome: Success août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.294603Z INFO _: Response succeeded. août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.301729Z INFO rocket::rocket: GET /static/cached/740aac32/css/default-light/fonts/Shabnam_WOL/Shabnam_WOL.css text/css: août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.301832Z INFO _: Matched: GET /static/cached/<_build_id>/css/<file..> (theme_files) août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.301926Z INFO _: Outcome: Success août 21 22:35:39 twili-services plume[27549]: 2022-08-21T20:35:39.302026Z INFO _: Response succeeded. ``` So if I get things right, Rocket is finding the route to the article. Or am I missing something? Any idea what could have went wrong? Do you think there might be a solution I could apply to fix the situation?
freyja_wildes commented 2022-08-21 21:37:58 +00:00
Author
Copy link

Also, some new posts have been made succesfully on the instance by a different user

Also, some new posts have been made succesfully on the instance by a different user
freyja_wildes commented 2022-08-31 20:40:42 +00:00
Author
Copy link

Ok, so I found the issue.
The original article title is:
"Un séjour hospitalier bipolaire 2 avec TDI/ATDS*"

You'll notice there's a '/' in there. That slash is of course then coded in the URL to a "%2F". But then, the routing can't happen properly. I don't know why, I don't understand the inner of the software well enough.

I am changing the title of the issue to be reflexive of the true issue.

Ok, so I found the issue. The original article title is: "Un séjour hospitalier bipolaire 2 avec TDI/ATDS*" You'll notice there's a '/' in there. That slash is of course then coded in the URL to a "%2F". But then, the routing can't happen properly. I don't know why, I don't understand the inner of the software well enough. I am changing the title of the issue to be reflexive of the true issue.
freyja_wildes changed title from Existing, listed article returns 404 on link to Special character '/' allowed in article title causes 404 2022-08-31 20:41:23 +00:00
KitaitiMakoto commented 2022-12-31 16:51:36 +00:00
Owner
Copy link

I recognize this issue and hope upgrading Rocket to v 0.5 solve this...

I recognize this issue and hope upgrading Rocket to v 0.5 solve this...
KitaitiMakoto added this to the 0.8.0 milestone 2023-01-01 06:32:01 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
1686a/resist-gone-sender
1686a/fast-fill
paginate-search-init
s3
fix-delete-user
timeline-cli
blog-title
signature
remove-dup-images
ldap-non-anon
drone-ci
DearRude/force-lang
igalic/go/async-all-mut
go/async
floreal/translations-update
missing-docs
RAOF/fix-arm64-build
epsilon-phase/authorized-fetch
upgrade
improve-the-editor-once-again
igalic/feat/custom-fairing-domains
feature/ldap
test/dotenv_error
fix-mobile-margin
0.7.2
0.7.1
0.7.0
0.6.0
0.5.0
0.4.0-alpha-4
0.3.0-alpha-2
0.2.0-alpha-1
Labels
Clear labels   
A: API

Related to the REST API

  
A: Backend

Code running on the server

  
A: Federation

Stuff related to Federation

  
A: Front-End

Related to the front-end

  
A: I18N

Translations, and related code

  
A: Meta

More about project management or code than the project itself

  
A: Security

   
Build

The building, or installation process of Plume

  
C: Bug

Something isn't working

  
C: Discussion

We need to talk

  
C: Enhancement

New feature or request

  
C: Feature

This is a new feature

  
Compatibility

Compatibility with different browsers, readers and OS

  
Dependency

Related to an external package that Plume uses

  
Design

UI/UX related issues and PRs

  
Documentation

   
Good first issue

Good for newcomers

  
Help welcome

Extra attention is needed

  
Mobile

Issues affecting only mobile UX

  
Rendering

How elements're rendered out for the end user

  
S: Blocked

Something else needs to be fixed first

  
S: Duplicate

This issue or pull request already exists

  
S: Incomplete

This PR is not complete yet

  
S: Instance specific

Issues concern a limited number of instances

  
S: Invalid

This doesn't seem right

  
S: Needs Voting/Discussion

Need to be discussed by the community (on Loomio)

  
S: Ready for review

This PR is ready to be reviewed

  
Suggestion

Proposed ideas worth considering

  
S: Voted on Loomio

This is issue has been created after a vote on Loomio

  
S: Wontfix

This will not be worked on

No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Milestone
Clear milestone
No items
No milestone
0.8.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#1111
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?