StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9351379
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
20
CommunityOwnedDate
CreationDate
2012-02-19T17:26:32.907
FavoriteCount
0
LastActivityDate
2012-02-21T14:29:00.300
LastEditDate
2012-02-21T14:29:00.300
LastEditorUserId
10333
OwnerUserId
10333
ParentId
9351219
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Yes... this is off the top of my head. Note, that I'm proxying to port 80 since most websites serve on port 80. Change the code for your specific use case. This is in CoffeeScript. Log Request Headers: <pre><code>fs = require('fs') httpProxy = require('http-proxy') fsw = fs.createWriteStream('myfile.txt', flags: 'a', mode: 0666, encoding: 'utf8') server = httpProxy.createServer (req, res, proxy) -> req.connection.pipe(fsw) #runs in parallel with the proxy... don't you love Node.js? proxy.proxyRequest(req, res, { host: require('url').parse(req.url).hostname, port: 80 }) server.listen(8080) </code></pre> <a href="http://coffeescript.org/#try%3afs%20%3D%20require%28%27fs%27%29%0AhttpProxy%20%3D%20require%28%27http-proxy%27%29%0A%0Afsw%20%3D%20fs.createWriteStream%28%27myfile.txt%27%2C%20flags%3A%20%27a%27%2C%20mode%3A%200666%2C%20encoding%3A%20%27utf8%27%29%0Aserver%20%3D%20httpProxy.createServer%20%20%28req%2C%20res%2C%20proxy%29%20-%3E%0A%20%20%20%20%20%20%20%20%20%20%20req.connection.pipe%28fsw%29%20%23runs%20in%20parallel%20with%20the%20proxy...%20don%27t%20you%20love%20Node.js%3F%0A%20%20%20%20%20%20%20%20%20%20%20proxy.proxyRequest%28req%2C%20res%2C%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20host%3A%20require%28%27url%27%29.parse%28req.url%29.hostname%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20port%3A%2080%0A%20%20%20%20%20%20%20%20%20%20%20%7D%29%0Aserver.listen%288080%29" rel="nofollow">JS Translation</a> Put 'localhost' and port 8080 for your browser proxy. Does this work for you? Log Request Body: <pre><code>fs = require('fs') httpProxy = require('http-proxy') server = httpProxy.createServer (req, res, proxy) -> body = '' req.on 'data', (chunk) -> body += chunk req.on 'end', -> fs.writeFile('mybody.txt', body, 'utf8') proxy.proxyRequest(req, res, { host: require('url').parse(req.url).hostname, port: 80 }) server.listen(8080) </code></pre> I tested this and can confirm that it logs the body of a POST/PUT. Log Response Body: <pre><code>fsw = fs.createWriteStream('myfile.txt', flags: 'a', mode: 0666, encoding: 'utf8') server = httpProxy.createServer (req, res, proxy) -> oldwrite = res.write res.write = (data, encoding, fd) -> fsw.write(data) res.write = oldwrite res.write(data, encoding, fd) res.write = oldwrite #<--- patch again before we leave the method proxy.proxyRequest(req, res, { host: require('url').parse(req.url).hostname, port: 80 }) server.listen(8080) </code></pre> Might not be the cleanest way, but I can confirm that it works.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POnode.js proxied request body
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJP Richardson
UserOwnerUserId
1. USJP Richardson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POnode.js proxied request body
 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
 VTModeratorReview
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.