StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMod Rewrite Producing 404 When Crawled (works fine when viewed in browser)
primarykey
Id
3645411
data
AcceptedAnswerId
3645428
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-05T08:04:45.687
FavoriteCount
0
LastActivityDate
2010-09-05T08:46:45.823
LastEditDate
2010-09-05T08:46:45.823
LastEditorUserId
439938
OwnerUserId
439938
ParentId
0
PostTypeId
1
Score
0
ViewCount
189
LastEditorDisplayName
text
Body
I have the following code in my .htaccess: <pre><code>RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </code></pre> My pretty-link converting is done on my index.php. If the user is looking for something that doesn't exist, a 404 Header is produced, otherwise content is show. That is all fine and dandy, however when a crawler or something tries to view the HTML, they are getting a 404 error. For example: <a href="http://www.jasonleodurbin.com/portfolio" rel="nofollow noreferrer">http://www.jasonleodurbin.com/portfolio</a> That link should work fine. If you try to validate it at an HTML validator, it doesn't work. The crawler says it is getting a 404. I am getting the same for Facebook share. I've tried removing the 404 error header, and I am still getting the same problem. What is the deal? Any suggestions? EDIT: New .htaccess: <pre><code>RewriteEngine On RewriteCond %{HTTP_HOST} ^jasonleodurbin\.com$ [NC] RewriteRule ^(.*)$ http://www.jasonleodurbin.com/$1 [R=301,L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^([a-z]+)/$ index.php?go=$1&app=1 [NC,L,QSA] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^([a-z]+)?success=true index.php?go=$1&success=1 [NC,L,QSA] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^([a-z]+) index.php?go=$1 [NC,L,QSA] </code></pre> Processing: globals.php <pre><code>if(!isset($_GET['go']) || $_GET['go'] == "") $_GET['go'] = "home"; </code></pre> header.php <pre><code>if(isset($_GET['go']) && !@fopen(strtolower($_GET['go']).".php",'r')){ //header("HTTP/1.0 404 Not Found"); define("FAIL",true); $_GET['go'] = "error"; } else { define("FAIL",false); Header('HTTP/1.1 200'); } if(FAIL) define("GOSUB",DIR); if(isset($_GET['app'])) define("GOSUB","../"); else define("GOSUB",""); </code></pre> I've also tried this for the index.php: <pre><code><?Header('HTTP/1.1 200 OK');?> <? require_once("header.php");?> <? require_once(strtolower($_GET['go'].".php"));?> </div> </div> <? if(!defined("FOOTER"))define('WP_USE_THEMES', false); define("FOOTER",true); include("blog/index.php"); ?>   </body> </html> </code></pre> Something is sending the 404 before I can even send 200.
Tags
<php><.htaccess><mod-rewrite><web-crawler>
Title
Mod Rewrite Producing 404 When Crawled (works fine when viewed in browser)
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USJason
UserOwnerUserId
1. USJason
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
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.