StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11133258
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-21T07:13:36.743
FavoriteCount
0
LastActivityDate
2012-06-21T07:13:36.743
LastEditDate
LastEditorUserId
0
OwnerUserId
217711
ParentId
11131403
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I do not consider exposing user IDs to public as a security flaw, there should be other mechanisms for security. Maybe it is a "marketing security flaw" when visitors find out you do not have that million users they promise ;-) Anyway: To avoid IDs in urls at all you can use the user's login in all places. Make sure the login does not contain some special characters (<code>./\#?</code> etc.), that cause problems in routes (use a whitelist regex). Also login names may not be changed later, that can cause trouble if you have hard links/search engine entries to your pages. Example calls are <code>/users/Jeff</code> and <code>/users/Jeff/edit</code> instead of <code>/users/522047</code> and <code>/users/522047/edit</code>. In your user class you need to override the <code>to_param</code> to use the login for routes instead of the user's id. This way there is no need to replace anything in your routes file nor in helpers like <code>link_to @user</code>. <pre><code>class User < ActiveRecord::Base def to_param self.login end end </code></pre> Then in every controller replace <code>User.find</code> by <code>User.find_by_login</code>: <pre><code>class UsersController < ApplicationController def show @user = User.find_by_login(params[:id]) end end </code></pre> Or use a <code>before_filter</code> to replace the params before. For other controllers with nested resources use <code>params[:user_id]</code>: <pre><code>class UsersController < ApplicationController before_filter :get_id_from_login def show @user = User.find(params[:id]) end private # As users are not called by +id+ but by +login+ here is a function # that converts a params[:id] containing an alphanumeric login to a # params[:id] with a numeric id def get_id_from_login user = User.find_by_login(params[:id]) params[:id] = user.id unless user.nil? end end </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORuby on Rails security vulnerability with user enumeration via id
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USarnep
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORuby on Rails security vulnerability with user enumeration via id
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.