Feedfetcher/HTTPClient fix
This fixes a typo which made the new Feedparser not use our own HTTPClient. It also enhances the get() method of HTTPClient to optionally cope better with bad HTTP responses: Some servers return a body with a "304 Not Modified" status which violates RFC 2616 but is usually accepted by common browsers. Setting the $sloppy304 parameter will return the response body. This fixes problems with feeds from feedblendr.com darcs-hash:20060429155805-7ad00-33a1c3142f241bf7747e8f679237cb6e8f1564ef.gz
Loading
Please register or sign in to comment