StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12476043
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
9
CommunityOwnedDate
CreationDate
2012-09-18T11:23:46.053
FavoriteCount
0
LastActivityDate
2012-09-18T13:25:18.443
LastEditDate
2012-09-18T13:25:18.443
LastEditorUserId
193376
OwnerUserId
193376
ParentId
12400792
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<h1>HTTPS suggestion</h1> For your HTTPS issue I would match on port or HTTPS as there are known apache problems relating to the HTTPS tag. To cover this match on both (as shown in your edited answer) <pre><code>RewriteCond %{SERVER_PORT} !^443$ [OR] RewriteCond %{HTTPS} != on ##REWRITE RULE RewriteCond %{SERVER_PORT} ^443$ [OR] RewriteCond %{HTTPS} = on ##REWRITE RULE </code></pre> A valid point is also that <code>%{REQUEST_URI}</code> isn't affected by any substitutions. The way you are using it at the moment, if any rule matches you will send them to the original url (before any substitution started). If you want to take the url after and substition and matching use <code>$1</code> <hr> Answers to your further questions: <h1>If I change the case of rewrite URL then it gives error?</h1> This is because your <code>[NC]</code> isn't on the rewrite cond for the HTTPS section of your .htaccess You match <code>RewriteCond %{REQUEST_URI} /login [OR]</code> this is only looking for lower case login, if you want to accept uppercase login append NC. <hr> <h1>Is it good practice to write [NC,L] with all RewriteRule?</h1> No, it depends what you want to do <code>[NC]</code> says don't match case on this rule, if you don't want to match case on that rule (or condition) then add it. Not matching the case with <code>[NC]</code> means site.com/login.php = sYte.cOm/LoGin.PHP <code>[L]</code> means if this is true, stop processing everything <hr> <h1>Exactly when I should write [QSA] ?</h1> QSA applies when you have a ? in your substitution and you want to append toe old string to the new URL Consider the following rule: <pre><code>RewriteRule /pages/(.+) /page.php?page=$1 [QSA] </code></pre> With the <code>[QSA]</code> flag, a request for <code>/pages/123?one=two</code> will be mapped to <code>/page.php?page=123&one=two</code>. Without the [QSA] flag, that same request will be mapped to <code>/page.php?page=123</code> - that is, the existing query string will be discarded. Do use QSA if you want to keep any additional get arguments. <hr> Another further question <h1>/login URL always changed into /login.php</h1> The only way for this to happen is if you have a redirect <code>[R=301]</code> somewhere in your code, the only place I can see that is this section: <pre><code># Rewrite to https RewriteCond %{SERVER_PORT} !^443$ [OR] RewriteCond %{HTTPS} != on RewriteCond %{REQUEST_URI} (/login|/do_login)\.php [NC] RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] </code></pre> Where this will only match the following URL's .php, /login.php, /do_login.php I believe the culprit is as I outlined in the first response with <code>%{REQUEST_URI}</code> Your code essentially says, if these conditions are met, send them to https://theurltheywentto, which is not what you want to do, you want to send them to /login. Have you tried using (as mentioned in my https section) <pre><code>RewriteRule ^(.*) https://%{HTTP_HOST}/login [R=301,L] </code></pre> Or perhaps (if you have /do_login) and other options <pre><code>RewriteRule ^(.*).php https://%{HTTP_HOST}/$1 [R=301,L] </code></pre> Where test.com/do_login.php will become <a href="https://test.com/do_login" rel="nofollow">https://test.com/do_login</a> How about you try: <pre><code># Rewrite to https RewriteCond %{REQUEST_URI} (/login|/do_login)\.php [NC] RewriteCond %{HTTPS} != on RewriteRule ^(.*)\.php https://%{HTTP_HOST}/$1 [R=301,L] </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORewriteRule violates while switching from https to http
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPez Cuckow
UserOwnerUserId
1. USPez Cuckow
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORewriteRule violates while switching from https to http
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.