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

Open
opened 2 years ago by freyja_wildes · 3 comments

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?
Poster

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
Poster

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 2 years ago
Owner

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 1 year ago
Sign in to join this conversation.
No Milestone
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
Loading…
There is no content yet.