StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
308070
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-11-21T06:50:59.257
FavoriteCount
0
LastActivityDate
2008-11-21T06:59:09.223
LastEditDate
2008-11-21T06:59:09.240
LastEditorUserId
2766176
OwnerUserId
2766176
ParentId
308059
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
brian d foy
text
Body
HTTP and CGI are different things. The Perl CGI module calls what it does an "HTTP header", but it's really just a CGI header for the server to fix up before it goes back to the client. They look a lot alike which is why people get confused and why the CGI.pm docs don't help by calling them the wrong thing. Apache fixes up the CGI headers to make them into HTTP headers, including adding the HTTP status line and anything else it might need. If you webserver isn't fixing up the header for you, it's probably expecting a "no-parsed header" where you take responsibility for the entire header. To do that in CGI.pm, you have to add the <code>-nph</code> option to your call to header, and you have to make the complete header yourself, including headers such as <code>Expires</code> and <code>Last-Modified</code>. See the docs under <a href="http://search.cpan.org/~lds/CGI.pm-3.42/CGI.pm#CREATING_A_STANDARD_HTTP_HEADER:" rel="nofollow noreferrer">Creating a Standard HTTP Header</a>. You can turn on NPH in three ways: <pre><code>use CGI qw(-nph) CGI::nph(1) print header( -nph => 1, ...) </code></pre> Are you using an older version of IIS? CGI.pm used to turn on the NPH feature for you automatically for IIS, but now that line is commented out in the source in CGI.pm: <pre><code># This no longer seems to be necessary # Turn on NPH scripts by default when running under IIS server! # $NPH++ if defined($ENV{'SERVER_SOFTWARE'}) && $ENV{'SERVER_SOFTWARE'}=~/IIS/; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy do I need to explicitly output the HTTP header for IIS but not Apache?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbrian d foy
UserOwnerUserId
1. USbrian d foy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy do I need to explicitly output the HTTP header for IIS but not Apache?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.