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
22440	Incorrect Behavior of ConditionalGetMiddleware	Mark Lavin	Mark Lavin	"There is an edge case where the {{{ConditionalGetMiddleware}}} violates RFC 2616 in particular http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.26

> If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status, then the If-None-Match header MUST be ignored.

The middleware currently does not check the original response status code before the If-None-Match. This is correctly handled by the {{{CommmonMiddleware}}} which has a similar check. This was pointed out in #12789 which tried to fix/address a related but seperate problem with how the ETag is actually generated. #17834 currently tracks problems with the generation of the ETag and this issue only tracks the problem with {{{ConditionalGetMiddleware}}} using the ETag however it may have been generated"	Bug	closed	HTTP handling	dev	Normal	fixed			Accepted	1	0	0	0	0	0