15329 2023-12-19 20:48:35 +0000 Default https://localhost:8081/accounts/login throws a 403 error; CSRF_TRUSTED_ORIGINS needs the port appended 2026-05-14 14:57:39 +0000 1 1 6 Yocto Project Subprojects Layer Index Layer Index 5.0 x86 Multiple NEW Medium+ normal 6.1 M2 1 tim.orling tim.orling piotr randy.macleod apoorvsangal --- --- Don't know oldest_to_newest 97626 0 tim.orling 2023-12-19 20:48:35 +0000 With the introduction of CSRF_TRUSTED_ORIGINS in Django 4.2, a default 'dockersetup.py' installation will set the port to 8081 and the hostname will be localhost. When logging in, this will result in a 403 error: Origin checking failed - https://localhost:8081 does not match any trusted origins. In order for this combination to work, CSRF_TRUSTED_ORIGINS = ['https://' + os.getenv('HOSTNAME', 'layers.test'), 'https://localhost:8081'] would have to be the setting. The fix should be in making the dockersetup.py script smart enough to append the port conditionally if it is not the default 80 or 443. 100941 1 randy.macleod 2025-02-13 16:05:16 +0000 Michael, is this something you can do on the systems that run the layer index? 100942 2 mhalstead 2025-02-13 18:49:23 +0000 As far as I understand this issue is not a problem for production deployments including the main one at layers.openembedded.org. I can have a look next time I set up a test instance but I hope a developer beats me to it. 104418 3 tim.orling 2026-02-26 16:09:38 +0000 We're likely moving away from the dockersetup.py script to .env files and docker-compose. I think the .devcontainer work by Piotr completely avoids this particular problem? 104555 4 piotr 2026-03-06 18:22:22 +0000 This does not seem to be a problem with the current Dev Container setup and shouldn't be a problem if deployed using docker/settings.py, as this property is derived from HOSTNAME env variable (with backwards compatible default). When using default, out-of-the-box setup for Dev Container, log in works without any issues.