id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
35579	Run the development server (python manage.py runserver) creating  http://127.0.0.1:8000/login/ in your browser.	clay richmond		"Potential Bug Report for Django (4.2.13)
Title: Unexpected ""Page not found (404)"" error for ""/login/"" path even without login functionality enabled.

Description:

This bug report describes an issue where Django (version 4.2.13) throws a ""Page not found (404)"" error for the path ""/login/"" even when the project doesn't utilize Django's built-in login functionality. The mysite/urls.py file does not define a URL pattern for login, yet the error persists.

Steps to Reproduce:

Create a new Django project (using django-admin startproject mysite).

In mysite/settings.py, ensure there are no configurations related to login functionality (e.g., no LOGIN_URL setting).

In mysite/urls.py, define only URL patterns for desired functionalities (excluding login). For example:

Python
from django.contrib import admin
from django.urls import path

urlpatterns = [
    path(""admin/"", admin.site.urls),
    # Other URL patterns for your app views
]
Use code with caution.
content_copy
Run the development server (python manage.py runserver).

Access the URL http://127.0.0.1:8000/login/ in your browser.

Expected Behavior:

Django should not generate a ""Page not found"" error for ""/login/"" as the project doesn't have a login URL pattern defined.
Actual Behavior:

Django displays a ""Page not found (404)"" error for ""/login/"".
Additional Information:

Python version: [Mention your Python version]
Operating System: macOS
Django version: 4.2.13
Possible Causes (for investigation):

Conflicting URL patterns in other apps (if applicable).
Third-party app interference with URL resolution.
Unexpected behavior in core Django routing logic (less likely).
Severity:

Medium (Disrupts development workflow and might cause confusion for users encountering the error).

Workaround (if applicable):

Manually remove any login URL patterns defined in other app-specific urls.py files.
Request:

Investigate the cause of the unexpected ""Page not found"" error for ""/login/"" when login functionality is not explicitly used.
Provide a potential fix or workaround if this is a bug in Django's core behavior.
Please note: This is a potential bug report based on the information provided. You might need to modify it based on your specific project setup and any additional details you discover.




tune

share


more_vert
"	Uncategorized	closed	Uncategorized	5.0	Normal	invalid			Unreviewed	0	0	0	0	0	0