#10305 closed enhancement (fixed)
Not all paged feeds return 404
| Reported by: | neoxx | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.1 |
| Component: | Feeds | Version: | 2.8 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
hi folks,
i implemented a map feature for my posts based on my weblog's feeds. as the number of posts certainly increased, i see the need for paging. fortunately this can be done by /feed/?paged=n and a check if the specific feed-page exists (if it doesn't throw a 404).
this works just fine for the general feeds like mydomain.com/feed/?paged=n and date-based queries mydomain.com/2009/feed/?paged=n. though, regarding the paged comments, tags and categories feeds, the aforementioned existence-check does not work, as these feeds return a 200 instead of a 404.
could someone kindly check this behaviour?
thanks,
berny
Change History (4)
#3
in reply to: ↑ 2
@
16 years ago
- Keywords close removed
- Resolution → fixed
- Status new → closed
Replying to solarissmoke:
This seems to be sorted in trunk - although I'm not entirely sure why feeds should allow paging in the first place..
general feeds, date-based queries, tags and categories feeds now return a clean 404
comments are not paged anyway.
thanks for fixing somewhere else :)
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This seems to be sorted in trunk - although I'm not entirely sure why feeds should allow paging in the first place..