StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18851370
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-17T13:34:02.307
FavoriteCount
0
LastActivityDate
2013-09-18T15:06:53.253
LastEditDate
2013-09-18T15:06:53.253
LastEditorUserId
303305
OwnerUserId
303305
ParentId
18831024
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I could not find a way to configure IIS, but I did find a workaround using an asp.net generic handler (<a href="http://forums.asp.net/p/1478217/3453189.aspx" rel="nofollow">http://forums.asp.net/p/1478217/3453189.aspx</a>, scroll down to the answer by gvlahakis). First, create a generic handler that returns 404: <pre><code>public class DirectoryBrowsingAttempt : IHttpHandler { public bool IsReusable {get {return true;} public void ProcessRequest(HttpContext context) {context.Response.StatusCode = 404;} } </code></pre> Second, add tags to the web.config to point directory browsing attempts to the above handler, one for each folder that you need to protect, in both the httpHandlers and system.webServer sections. The tags below protect a folder named "js" off of the root. <pre><code><httpHandlers> <add verb="*" path="js/*" validate="false" type="MyNameSpace.DirectoryBrowsingAttempt"/> </httpHandlers> <system.webServer> <handlers> <add name="NoAccess" verb="*" path="js/*" preCondition="integratedMode" type="MyNameSpace.DirectoryBrowsingAttempt"/> </handlers> </code></pre> This workaround behaves differently in IIS 6 vs. IIS 7. For example, I protected a folder that contained the site's images in this manner: IIS 6 still delivered the images contained in this folder to web pages (the desired behavior, I just want to block directory browsing attempts); IIS 7 blocked them. There are probably ways to use the "location" tab in the web.config to allow images to be served up by overriding the default image handler, but I've no desire to go that far down the rabbit hole.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConfigure IIS to return 404 for directory browse attempts
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTom Regan
UserOwnerUserId
1. USTom Regan
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.