Context Navigation

Changes between Initial Version and Version 1 of Ticket #27379, comment 2

initial	v1
42	42	}}}
43	43
44		Django chooses not to honour this request cause the host-header is not configured as it expects it too. This is a valid reason to reject the request, cause after all a valid client MUST send a valid host-header and technically is not allowed to send a full request URI. So unless there is any evidence that this has legitimate use cases, I suggest we leave it as is to keep the code simple. ~~Another interesting sidenote: How is the server supposed to know if `http://example.com` is a full URI or actually a path named `http://example.com`?~~
	44	Django chooses not to honour this request cause the host-header is not configured as it expects it too. This is a valid reason to reject the request, cause after all a valid client MUST send a valid host-header and technically is not allowed to send a full request URI. So unless there is any evidence that this has legitimate use cases, I suggest we leave it as is to keep the code simple.