Databases
StackOverflow2013
Postsdbo
POForward users who use WWW in URL
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POForward users who use WWW in URL
    primarykey
    data
    text
    <p>Every user on my website get its own URL for usernames like <code>username.example.com</code>. I know that sometimes people are typing <code>www</code> in front the URL. When users do that, they will get redirected by the system to the frontpage. Is there a way to (1) detect the use of <code>www</code>, (2) the username and (3) forward the user to <code>username.example.com</code>, NOT <code>www.username.example.com</code> with PHP?</p> <p>This is not a DNS-releated question.</p> <pre><code>RewriteEngine On Options +Followsymlinks RewriteBase / RewriteCond %{HTTP_HOST} . RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteCond %{REQUEST_FILENAME} !^.*/images/.*$ RewriteCond %{REQUEST_FILENAME} !^.*/uploads/.*$ RewriteCond %{HTTP_HOST}&lt;&gt;%{REQUEST_URI} ^([^.]+)\.bloggify\.no(:80)?&lt;&gt;/([^/]*) [NC] RewriteCond %1&lt;&gt;%3 !^(.*)&lt;&gt;\1$ [NC] RewriteRule ^(.*)$ - [E=BLOGUSER:%1] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^$ /index.php?w=%1 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^page([0-9]+)/([^/]+)?$ /index.php?w=%1&amp;page=$1$2 [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^profiles/([^/]+)/([^/]+)?$ /profile.php?u=$1$2 [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^profiles/?$ /profile.php [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^albums/([^/]+)/([^/]+)?$ /album.php?u=$1$2 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^archive/(.*)/(.*)/([^/]+)?$ /archive.php?w=%1&amp;y=$1&amp;m=$2$3 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^archive\.php/(.*)/(.*)/([^/]+)?$ /archive.php?w=%1&amp;y=$1&amp;m=$2$3 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^archive/(.*)/([^/]+)?$ /archive.php?w=%1&amp;y=$1$2 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^archive\.php/(.*)/([^/]+)?$ /archive.php?w=%1&amp;y=$1$2 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^archive/([^/]+)?$ /archive.php?w=%1$1 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^archive\.php/([^/]+)?$ /archive.php?w=%1$1 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^friends/([^/]+)?$ /friends.php?w=%1$1 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^friends\.php/([^/]+)?$ /friends.php?w=%1$1 [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^([^/]+)/friends/page([0-9]+)/([^/]+)?$ /friends.php?w=$1&amp;page=$2$3 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^([0-9]+)/([^/]+).html$ /entry.php?w=%1&amp;e_id=$1 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^([0-9]+)/([^/]+)?$ /entry.php?w=%1&amp;e_id=$1$2 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^&amp;([^/]+)?$ /index.php?w=%1&amp;$1 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^([^/]+)/([^/]+)?$ /index.php?w=%1&amp;category=$1$2 [L] RewriteCond %{ENV:BLOGUSER} ^(.+)$ RewriteRule ^([^/]+)/page([0-9]+)/([^/]+)?$ /index.php?w=%1&amp;category=$1&amp;page=$2$3 [L] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser2261044
    1. USuser2261044
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COPHP does not run the web server. Check what product you are using to host your website. Apache is commonly used for this purpose.
      singulars
      1. POForward users who use WWW in URL
      1. USGeorge
    2. CODon't tell your users that their URL is `username.example.com`. That's just plain wrong, `username.example.com` is not a valid URL. Tell your users, their URL is `http://username.example.com`. I suspect no one will then be tempted to use `http://www.username.example.com`
      singulars
      1. POForward users who use WWW in URL
      1. USOswald
    3. COThats trivial to "fix" with a rewrite rule http://stackoverflow.com/questions/234723/generic-htaccess-redirect-www-to-non-www
      singulars
      1. POForward users who use WWW in URL
      1. USAD7six
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload