StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POStrange behaviour between wamp and lamp (ubuntu)
primarykey
Id
20256842
data
AcceptedAnswerId
20338980
AnswerCount
2
ClosedDate
CommentCount
19
CommunityOwnedDate
CreationDate
2013-11-28T02:49:02.233
FavoriteCount
0
LastActivityDate
2013-12-02T22:52:14.583
LastEditDate
2013-12-02T22:52:14.583
LastEditorUserId
2186625
OwnerUserId
2186625
ParentId
0
PostTypeId
1
Score
-3
ViewCount
249
LastEditorDisplayName
text
Body
<p>Ever since I moved to Linux, I noted some strange behaviour. In Ubuntu, <code>http://localhost/index</code> works but on WAMP it does not work. <strong>I tested this with APACHE's rewrite module set to off on both</strong>. Any good explanation? <img src="https://i.stack.imgur.com/8CGi7.jpg" alt="Strange WAMP & LAM behavior"></p> <p>Apache.conf (LAMP)</p> <p>etc/apache2/sites-enabled/000-default</p> <pre><code><VirtualHost *:80> ServerAdmin webmaster@localhost DocumentRoot /var/www <Directory /> Options FollowSymLinks AllowOverride None </Directory> <Directory /var/www/> Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny allow from all </Directory> </code></pre> <p>Apache.conf WAMP</p> <pre><code><Directory "C:/wamp/www/"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.2/mod/core.html#options # for more information. # Options Indexes FollowSymLinks # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride all # # Controls who can get stuff from this server. # # onlineoffline tag - don't remove Order Allow,Deny Allow from all </Directory> </code></pre> <h1>EDIT: Why it behaves this way thanks to [tntu][2]</h1> <p>Because of the directive <code>Options Indexes FollowSymLinks MultiViews</code> on LAMP (ubuntu), the url localhost/index can resolve to the file index.php, index.html. So foo would also result into foo.php, foo.html. A proper explanation can be derived from <a href="http://httpd.apache.org/docs/current/content-negotiation.html" rel="nofollow noreferrer">http://httpd.apache.org/docs/current/content-negotiation.html</a></p> <h2>Don't be confused to think this is url rewriting</h2>
Tags
<php><url-rewriting><apache2><wamp><lamp>
Title
Strange behaviour between wamp and lamp (ubuntu)
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAlexander Kimaru
UserOwnerUserId
1. USAlexander Kimaru
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. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POStrange behaviour between wamp and lamp (ubuntu)
  UserUserId
  USAlexander Kimaru
  VoteTypeVoteTypeId
  VTBountyStart
2. VO
  singulars
  PostPostId
  POStrange behaviour between wamp and lamp (ubuntu)
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTApproveEditSuggestion
3. VO
  singulars
  PostPostId
  POStrange behaviour between wamp and lamp (ubuntu)
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTDownMod
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.