StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17113207
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-06-14T16:31:01.270
FavoriteCount
0
LastActivityDate
2013-06-16T23:14:20.607
LastEditDate
2013-06-16T23:14:20.607
LastEditorUserId
2334192
OwnerUserId
2334192
ParentId
17045241
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
By default the headers should not be written out with the body data. If your are receiving headers in your <code>write_data</code> callback, that probably means you've set either the <code>CURLOPT_HEADER</code> option or the <code>CURLOPT_WRITEHEADER</code> option. You could try resetting both of those to be safe: <pre><code>curl_easy_setopt(curl, CURLOPT_HEADER, 0L); curl_easy_setopt(curl, CURLOPT_WRITEHEADER, 0L); </code></pre> If you do still want to retrieve the headers, but just not in the <code>write_data</code> callback, you can set a separate callback for your header data like this: <pre><code>curl_easy_setopt(curl, CURLOPT_HEADERFUNCTION, write_header); </code></pre> Where <code>write_header</code> is a callback function, much like your <code>write_data</code> function. <pre><code>size_t write_header(void *ptr, size_t size, size_t count, void *stream) { printf("HEADER: %*.*s", size * count, size * count, ptr); return count*size; } </code></pre> Note that it's important you return the number of bytes written from these callback functions otherwise curl would treat that as an error. If this is still not working for you, the only other explanation I can think of is that your server is returning a blank line before the header data, making it seem as if the headers are actually part of the body. You easily see if that is the case by testing against a known valid url (e.g. <code>http://www.example.com/</code>). If it works correctly there, then you know the fault is in your server code and not the client code. Having looked at your full code, though, all of that extra stuff you're seeing in your output is coming from the <code>CURLOPT_VERBOSE</code> options (which you've set twice), and <code>CURLOPT_NOPROGRESS</code> option. Just comment those out and you should get a nice clean response with nothing but the content body. I should also mention that there's no point in setting <code>CURLOPT_FILE</code> unless you're going to be using the stream parameter in the <code>write_data</code> callback. When you set the <code>CURLOPT_WRITEFUNCTION</code> callback, it replaces the default output function, so nothing will get written to the <code>CURLOPT_FILE</code> stream unless you do so yourself.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCURLOPT_WRITEFUNCTION to get xml content
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJames Holderness
UserOwnerUserId
1. USJames Holderness
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. This table or related slice is empty.
CommentsPostId

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.