Unfortunately, you can't rely on a response code of 200 always indicating success - some web servers (I've heard) return that code even for a failed request.
It turns out that I'm testing a web application that I'm maintaining -- so the application is well behaved in that regard. I check that the status was OK, and also check that the content is what I was expecting.
And I expect to get a 200 Status even on a page that returns something like 'User not found' -- that isn't a protocol error, it's an application error. I also expect to get a 404 on a 'page not found' error, but for pages that are part of a package that may not be installed, that's OK. What I think you're describing is conflating an application error with a protocol error, which I don't think is right.
And now I know to read the part of the module deltas that say something like "This may break your code" much more closely. :)
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.