StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9598269
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-07T08:48:21.477
FavoriteCount
0
LastActivityDate
2012-03-07T08:48:21.477
LastEditDate
LastEditorUserId
0
OwnerUserId
613064
ParentId
9582892
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The HTTP protocol is really simple, actually: <ol> <li>the client sends a line containing HTTP method name, URL and protocol version</li> <li>the client sends an RFC822 header containing request parameters and, if a data block follows, details about the data block.</li> <li>the client sends the data block</li> <li>the server sends a line containing protocol version, status code and message</li> <li>the server sends an RFC822 header containing response parameters and, if a data block follows (or the client performed a HEAD request), details about the data block</li> <li>the server sends the data block, unless the method is HEAD.</li> <li>the connection is either torn down, or the protocol restarted.</li> </ol> Typically, servers will understand at least these methods: <ul> <li>GET (client does not send data block, server sends data block)</li> <li>HEAD (same as GET, but server omits response data block)</li> <li>POST (client sends data block, server responds with data block)</li> <li>PUT (client sends data block, server does not send data block)</li> </ul> There is some implied semantics in the choice of method, in that GET requests never modify server state and their results may be cached and reused (which is what allows the browser to go back and forth between pages), while POST requests do change server state -- incidentally, this is what you do when you upload a file. So, in order to send a file, prepare a POST or PUT request (depending on whether you expect a reply document, or if a simple acknowledgement status code is sufficient), which consists of the request line, the headers containing extra protocol info ("Host:", "User-Agent:", ...), the headers describing the file ("Content-Type:", "Content-Length:", ...), an empty line, and the file contents, and send that over a TCP connection, then read back the status line, the response headers and the response file (if you asked for one).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow http server received file from client
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSimon Richter
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
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.