StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13106009
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-28T02:53:49.007
FavoriteCount
0
LastActivityDate
2012-10-28T02:53:49.007
LastEditDate
LastEditorUserId
0
OwnerUserId
135978
ParentId
13018375
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
From what I can tell, this is a limitation of the way that WSGI works. The stream needs only be consumable once (<a href="http://www.python.org/dev/peps/pep-0333/" rel="nofollow">PEP 333</a> and <a href="http://www.python.org/dev/peps/pep-3333/" rel="nofollow">3333</a> only require that the stream support <code>read*</code> calls, <code>tell</code> does not need to be supported). Once the stream is exhausted it cannot be re-streamed to other WSGI applications further "inward". Take a look at these two sections of Werkzeug's documentation for more information: <ol> <li><a href="http://werkzeug.pocoo.org/docs/request_data/" rel="nofollow">http://werkzeug.pocoo.org/docs/request_data/</a></li> <li><a href="http://werkzeug.pocoo.org/docs/http/#module-werkzeug.formparser" rel="nofollow">http://werkzeug.pocoo.org/docs/http/#module-werkzeug.formparser</a></li> </ol> The way to avoid this issue is to wrap the input stream (<code>wsgi.input</code>) in an object that implements the <code>read</code> and <code>readline</code> methods. Then, only when the final application in the chain actually attempts to exhaust the stream will your methods be run. See <a href="http://flask.pocoo.org/docs/patterns/requestchecksum/" rel="nofollow">Flask's documentation on generating a request checksum</a> for an example of this pattern. That being said, are you sure a middleware is the best solution to your problems? If you need to perform some action (dispatch, logging, authentication) based on the content of the body of the request you may be better off making it a part of your application, rather than a stand-alone application of its own.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to access wsgi params from a request inside a middleware and a flask request without side effect?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSean Vieira
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to access wsgi params from a request inside a middleware and a flask request without side effect?
 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
 VTAcceptedByOriginator
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.