StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8456534
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-10T12:36:05.197
FavoriteCount
0
LastActivityDate
2011-12-10T13:03:26.927
LastEditDate
2011-12-10T13:03:26.927
LastEditorUserId
319403
OwnerUserId
319403
ParentId
8456475
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If you want to discourage some casual user from posting from someone else's site to yours, you might be able to check <code>$_SERVER['HTTP_REFERER']</code>. The browser sends a "referer" along with most requests, which in many cases is the page that the user clicked to get there. It's definitely not foolproof, though -- a browser (or a bot) can fudge it at will, and some browsers (or plugins for such browsers) will do so on purpose. The users of those browsers are generally pretty big on privacy, and you're not that special. They'll probably prefer going elsewhere rather than disabling their privacy stuff for you. You could require a session variable set in order to post, but that's rather trivial to get around too. <code><img src="http://your.site/yourForm.php" width="1" height="1"></code> would be enough to get a session variable set. A hidden form field sounds doable, but i could write a script to fetch your form, grab the hidden field, and insert it into my form. It'd only be useful in conjunction with a session variable that says what ID to expect...and that gets really wacky if people use the Back button in certain ways. It'd also fail if i proxy the request (ie: the user talks to my server, which requests a form from you (and gets a session ID), and then when the user posts to my site, i post to yours using the session ID and hidden values that you sent me). About the only way around that is HTTPS, and even that's useless if the user is expecting the form to come from me and not you. Basically, there's no way short of a combination of the above stuff plus a decent CAPTCHA to prevent other sites from posting to your form. And even that has its weaknesses. The best you can do is make it a pain...and that'll make it a pain for some percentage of your users as well. Your best bet is to make sure the script that accepts the post verifies its contents, and not care where the request came from.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to trace the request path of the form?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UScHao
UserOwnerUserId
1. UScHao
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
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.