[wp-trac] [WordPress Trac] #13049: Wordpress should not generate feeds for 404 pages

WordPress Trac wp-trac at lists.automattic.com
Sat Apr 24 06:12:02 UTC 2010


#13049: Wordpress should not generate feeds for 404 pages
--------------------------+-------------------------------------------------
 Reporter:  solarissmoke  |       Owner:              
     Type:  defect (bug)  |      Status:  new         
 Priority:  low           |   Milestone:  3.0         
Component:  Feeds         |     Version:  3.0         
 Severity:  normal        |    Keywords:  dev-feedback
--------------------------+-------------------------------------------------

Comment(by dd32):

 > No, the issue isn't with empty feeds.

 I think you mis-understood me, I was referring directly to set_404() not
 setting 404's for feeds.

 My understanding is that its to allow for the feed template to continue
 being loaded even when no posts exist for the request, but the actual
 request is still valid.

 For example, An empty category feed should still return an empty feed.
 which is different from a non-existant category, or resource, which this
 is about.

 ----

 > In either case, is_feed() and is_404() cannot be true at once.

 Well it can, is_404() being true refers to there being no posts/pages/etc
 to return for the current request, that does not mean that the request is
 a 404'able request however (In other words, WordPress is_404 is not the
 same as a 404 HTTP response in all cases). See WP::handle_404() for some
 cases where it doesnt pass it through.

 I do agree, that is_feed() should be false for a non-existant resource
 however.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13049#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list