|
Ever since the Humble Bundle, none of Paizo's RSS feeds have been working in Feedly. When I tell Feedly to go add them, it says they cannot be found, while viewing them directly in the browser still displays well-formed XML--I would expect it to be fine.
It gets a little stranger, though: while investigating what might be going on, I found that the Paizo servers are returning 404s for some types of requests and 200 for other requests of the same URL. Default wget fails while default curl works.
DEBUG output created by Wget 1.16.1 on linux-gnu.
URI encoding = ‘UTF-8’
--2016-03-11 15:50:59-- http://paizo.com/paizo/blog&xml=atom
Resolving paizo.com (paizo.com)... 207.115.69.198
Caching paizo.com => 207.115.69.198
Connecting to paizo.com (paizo.com)|207.115.69.198|:80... connected.
Created socket 3.
Releasing 0x00005599a2c57fe0 (new refcount 1).
---request begin---
GET /paizo/blog&xml=atom HTTP/1.1
User-Agent: Wget/1.16.1 (linux-gnu)
Accept: */*
Accept-Encoding: identity
Host: paizo.com
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 404 File Not Found
Date: Fri, 11 Mar 2016 20:54:29 GMT
Server: Apache
Vary: User-Agent
content-length: 99
Cache-Control: no-cache, private, no-store, must-revalidate, max-age=0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
pragma: no-cache
MS-Author-Via: DAV
Keep-Alive: timeout=15, max=500
Connection: Keep-Alive
Content-Type: text/html
---response end---
404 File Not Found
Registered socket 3 for persistent reuse.
Skipping 99 bytes of body: [<html><body><strong>The requested application was not found on this server.</strong></body></html>
] done.
2016-03-11 15:50:59 ERROR 404: File Not Found.
* Trying 207.115.69.198...
* Connected to paizo.com (207.115.69.198) port 80 (#0)
> HEAD /paizo/blog&xml=atom HTTP/1.1
> Host: paizo.com
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 Apple
HTTP/1.1 200 Apple
< Date: Fri, 11 Mar 2016 21:00:56 GMT
Date: Fri, 11 Mar 2016 21:00:56 GMT
< Server: Apache
Server: Apache
< cache-control: private
cache-control: private
< cache-control: no-cache
cache-control: no-cache
< cache-control: no-store
cache-control: no-store
< cache-control: must-revalidate
cache-control: must-revalidate
< cache-control: max-age=0
cache-control: max-age=0
< expires: Fri, 11-Mar-2016 18:00:45 GMT
expires: Fri, 11-Mar-2016 18:00:45 GMT
< pragma: no-cache
pragma: no-cache
< content-length: 386811
content-length: 386811
< MS-Author-Via: DAV
MS-Author-Via: DAV
< Content-Type: application/atom+xml
Content-Type: application/atom+xml
<
* Connection #0 to host paizo.com left intact
I'm not absolutely sure what's going on, but it strikes me as odd that for one of these two requests, the site returns an "application not found" error.
|
|
Hmm. Not that I have any idea what's going on in the back end (nor should I), but I briefly got excited because a different link showed up on the blog RSS link. It has since reverted, but I managed to dig it out of my history and it still works:
And I tried building a corresponding URL for the Pathfinder Design Team account, which also seems to work:
Pathfinder Design Team posts
