Static files aren't served correctly on dev server when DEBUG and FORCE_SCRIPT_NAME are enabled

[EugeneM]

Found out that the ticket was closed but still is interesting in mention about incorrectly truncated path in 404 message.

Why it's ok ?

[Natalia Bidart]

Hello Eugene, thanks for your ticket.

Could you please provide some more details on how to reproduce this issue? A description of the necessary setup and/or a small Django test project as a reproducer would be ideal.
Even better a regression test if you would be up for it!

For now I'll mark this report as needsinfo, but I'll reopen as soon as we have more information to properly triage this issue.

Thanks!

[Mariusz Felisiak]

As far as I'm aware this is a duplicate of #30634, #7930, #31724 and few other tickets.

[EugeneM]

Steps to reproduce:

• bootstrap

  mkdir tmp && cd tmp
  virtualenv venv
  . venv/bin/activate
  pip install "Django<5"
  django-admin startproject testme 10.100.100.10:9999
  cd testme && mkdir static && touch static/test.css
  

• nano testme/settings.py && add in the end of file and save

ALLOWED_HOSTS = ['*',]
STATICFILES_DIRS  = [ f'{BASE_DIR}/static' ]

• test if all is ok in browser: ​http://10.100.100.10:9999/static/test.css

• nano testme/settings.py # add in the end of file and save

FORCE_SCRIPT_NAME = '/sub'

• test in browser: ​http://10.100.100.10:9999/static/test.css and get "Page not found (404) 'tic/test.css' could not be found"

• do fix

• test if all is ok in browser: ​http://10.100.100.10:9999/static/test.css

• disable FORCE_SCRIPT_NAME and check ​http://10.100.100.10:9999/static/test.css

Replying to Mariusz Felisiak:

As far as I'm aware this is a duplicate of #30634, #7930, #31724 and few other tickets.

Just because somebody missed it long time ago doesn't mean it's ok.
"Page not found" message with incorrectly truncated file name hints that something went wrong.
Moreover if you can check request.path and 'request.path_path' and see a difference