# sign and, probably, other special characters are giving 404 on NGiNX Proxy. #1

Closed
opened 2021-02-17 02:11:22 +04:00 by Arav · 1 comment
Owner

Even being encoded to %23, a # sing makes NGiNX shit its pants and give out a 404 error. Googling haven't given a solution for it and I have no idea how to fix this.

Even being encoded to %23, a # sing makes NGiNX shit its pants and give out a 404 error. Googling haven't given a solution for it and I have no idea how to fix this.
Arav self-assigned this 2021-02-17 02:11:22 +04:00
Author
Owner

Okay, I "fixed" that by adding /files/ location in NGiNX and adding that prefix to all files. This way, files downloading is handled by NGiNX now, which is absolutely fine. Probably even will delete file handling in files.js, since NGiNX doing everything for it.

Okay, I "fixed" that by adding /files/ location in NGiNX and adding that prefix to all files. This way, files downloading is handled by NGiNX now, which is absolutely fine. Probably even will delete file handling in files.js, since NGiNX doing everything for it.
Arav closed this issue 2021-02-17 02:56:48 +04:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 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: Arav/Dwelling#1
No description provided.