fixes to conditionalhttp, et al
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
I noticed that conditionalhttp didn't seem to be working quite right. It was returning a 304 status code, but then seemed to render all the content again anyhow. I verified this behavior using ethereal and tracking the data passed back and forth. So I began to poke around and I fixed a minor bug in the blosxom renderer (it would render, mark as rendered, but never checked the flag that it had rendered already), then a minor bug in the conditionalhttp plugin (it didn't whack the content, so the content would be rendered along with the 304 status code), and then fixed a bug in the rss2renderer (same problem as with the blosxom renderer). Then I figured the rss2renderer should be in the contributed plugins pack, so I added that to the repository. I checked all the changes I made in. Anyhow, if you see any problems, let me know. On another note, what happened to the push to put out a new contributed plugins pack for pyblosxom 1.2? We promised that to the debian folks weeks ago. /will ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20