homepage Welcome to WebmasterWorld Guest from 54.198.224.121
register, free tools, login, search, subscribe, help, library, announcements, recent posts, open posts,
Subscribe and Support WebmasterWorld
Home / Forums Index / Code, Content, and Presentation / Apache Web Server
Forum Library, Charter, Moderators: Ocean10000 & incrediBILL & phranque

Apache Web Server Forum

This 42 message thread spans 2 pages: 42 ( [1] 2 > >     
Rewrite Dynamic Query String URL to Subdomain
Need to Rewrite Query String and 301 to Subdomain
ItsDavid




msg:4548745
 5:44 pm on Feb 25, 2013 (gmt 0)

Hi, I have finally given in and decided to ask here because my days are passing me by and i am not making any progress. I have been searching the internet for days trying to find answers related to my questions with very minimum results to my situation.

Before i get started with my questions i just want to add that i do have wildcard domains setup and working properly on my site and i also have a sub.domain.com setup in my cpanel for this exact url in question that points to the main sites root folder. So with that said Here We Go!


My current dynamic url structure is currently like this

index.php?a=11&b=$2&c=65&d=3


all urls must make the call to index.php

Now what i am trying to do is take this exact url below

index.php?a=4


and display it as a sub.domain.com which currently only works if i comment out the RewriteCond %{QUERY_STRING} ^a=4$ [NC]part of the rewrite rule. however when i go to the address sub.domain.com i am getting the following message in my browser.

The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.


Here is the code i am currently using to try to accomplish this.

RewriteCond %{HTTP_HOST} ^sub.domain.com? [NC]
RewriteCond %{REQUEST_URI} !^/accounts/.* [NC]
RewriteCond %{QUERY_STRING} ^a=4$ [NC]
RewriteRule ^/?index\.php$ http://sub\.domain.com? [L]


Now because this is a dynamic query string url i have to make two rewrite rules and this current 301 rewrite rule i have keeps crashing my server, why i don't know but every time i try different things to get the rule to work my server goes haywire but i don't get any messages in my browser like i do with the other code above. Here is the 301 rewrite i am trying to use but to no avail.

# Redirect Direct Client Requests For Account Dynamic URL to Static Equivalent Subdomain
RewriteCond %{QUERY_STRING} ^a=4$ [NC]
RewriteRule ^index\.php$ http://sub.domain.com? [R=301,L]


I need these rules to be exact matches specific to the sub.domain.com because i tried running it as a wildcard and it breaks my other wildcard subdomains that are currently setup for states and cities.

I have one other question as well that i would like to ask the experts here. The code below has nothing to do with the subdomain question as it is working fine however if you could just take a look at it and share your thoughts on it's structure? I am just curious if there is anything that can be done to make it better?

# Redirect Direct Client Requests For About Us Dynamic URL to Static Equivalent
RewriteCond %{THE_REQUEST} ^a=28&b=142$
RewriteRule ^index\.php$ http://wantadmag.com/about? [R=301,L]

RewriteRule ^about$ index.php?a=28&b=142 [L] ## About Us URL


Thank you all in advance for any help you can provide.

 

g1smd




msg:4548763
 6:16 pm on Feb 25, 2013 (gmt 0)

Now what i am trying to do is take this exact url below
index.php?a=4
and display it as a sub.domain.com

That is exactly backwards to how mod_rewrite works.

Mod_rewrite works with "requests". The request is sent by the browser after a link is clicked. You need a rule that responds when "sub.example.com" is requested. The rule will map that request to the internal location /index.php?a=4 so that content can be fetched.

You also need to ensure that the new internal request for /index.php?a=4 doesn't accidentally re-match any of your other rules, otherwise you end up with an infinite loop.

THE_REQUEST will never match a pattern like ^a=28&b=142$ so that rule never functions.
THE_REQUEST will be something like
GET /index.php?a=28&b=142 HTTP/1.1 as sent by the browser and you'll need a pattern to match that (usually begins ^[A-Z]{3,9}\ / and ends \ HTTP/ or similar).

Be sure you know the difference between a rewrite and a redirect (both are coded from RewriteRules) and be sure you know when you're dealing with URLs (as used on the web) and files and folders (as used inside the server). They are not at all the same thing; they are merely linked by the server configuration.

As the most often asked question here (at least 4 or 5 times in the last couple of weeks alone) there are many recent threads with additional useful information.

ItsDavid




msg:4548774
 7:08 pm on Feb 25, 2013 (gmt 0)

I was able to get another rewrite rule to actually work but the problem I had with it was that I had to use the [P] flag I then later on learned that it could lead to security issues I then contacted my hosting provider and asked them and their response was that anything proxy could lead to problems so I discarded that option.

So are you saying that there is no real way for me to display [sub.domain.com...] in the browser while in fact it would actually be pointing to [domain.com...]

g1smd




msg:4548776
 7:15 pm on Feb 25, 2013 (gmt 0)

I am saying your description was backwards which could lead to completely wrong code.

If you want to show sub.example.com in the browser address bar, you'll need to provide a link on the page of your site that points to that URL. Users will click the link, and their browser will make that request and show that URL in the address bar. mod_rewrite responds only when that request arrives at the server. mod_rewrite does not "make" URLs nor can it change the links on your pages.

What you want to do can be done in a few lines. The rule will respond when "sub.example.com" is requested and internally rewrite the request to fetch the content from /index.php?id=4 without revealing what that location is.

ItsDavid




msg:4548845
 11:29 pm on Feb 25, 2013 (gmt 0)

I think things are getting confused here as to what my request is and understanding of things are. I am aware of the basics and i also am knowledgeable as to the difference between files, folders, rewrites and redirects. I thought i explained that within my first post when i said that because they are dynamic urls i had to rewrite them first then redirect them. However maybe i didn't explain things clear enough in a way others would understand. I am horrible at explaining things sometimes.

I am basically looking for suggestions, examples feedback etc...

I mentioned above that i was also rewriting other links the About Us link and they seem to be working great with the example i posted but again with that rewrite then redirect of the old About Us url i am looking for more experienced people to look it over then maybe provide some examples, advice on how to make it better if there are any ways it can be improved.

With that said i also want to thank you for the advice you have provided and i am going to take your suggestion and see if i can roll them into a real working example.

g1smd




msg:4548848
 11:56 pm on Feb 25, 2013 (gmt 0)

In the last week, 7 or 8 variants of this queation have been asked so there's multiple parallel threads with similar code to look through.

ItsDavid




msg:4548849
 12:12 am on Feb 26, 2013 (gmt 0)

I have to say that if that is the case I apologized for starting another thread but I truly have been searching every term possible related to

Rewrite Query String to Subdomain

Redirect Query String to Subdomain

Rewrite Query String URL That requires index.php

And many many more for about the last week and the only results I can locate is rewriting or redirecting sub folders or directories to some sub.domain.com to domain.com/mynewurl or sub.domain.com/this.php?=NewURL.

This is the first place I decided to ask because I couldn't find any search results related to my situation. But if they are out there would you mind pointing me in the right direction as maybe I am just not searching for the correct terms.

lucy24




msg:4548850
 12:17 am on Feb 26, 2013 (gmt 0)

Ouch. I'm getting a headache just trying to read the post.
My current dynamic url structure is currently like this
index.php?a=11&b=$2&c=65&d=3

b=$2 ? Is that a literal dollar sign, or have you got a capture #2 from somewhere else?

Just because you can put something in a query string-- never mind the path part of the URL-- doesn't mean you should do it. Stick with alphanumerics and you will have no worries.


Now what i am trying to do is take this exact url below

index.php?a=4

Didn't you just get through saying that your ordinary URL has four parameters? Are they each optional?


RewriteCond %{HTTP_HOST} ^sub.domain.com? [NC]
RewriteCond %{REQUEST_URI} !^/accounts/.* [NC]
RewriteCond %{QUERY_STRING} ^a=4$ [NC]
RewriteRule ^/?index\.php$ http://sub\.domain.com? [L]


This is the point where I try to pick apart the rule and see what it does as written.

IF mod_rewrite encounters a request for "www.example.comindex.php" or "www.example.com/index.php" -- assuming the rule is located in the config file -- or for "www.example.com/index.php" or "www.example.com//index.php" -- if the rule is located in the domain's root-level .htaccess -- or for "www.example.com/directory/index.php" or "www.example.com/directory//index.php" -- if the rule is located in the htaccess of a deeper directory...

THEN evaluate the conditions.

#1 IF all this is happening in the (sub)domain "sub.domain.com" or "subxdomainxcom" or "subodomain.co" or ... well, I make it 3042 possible permutations. Put away the calculator. I used (26+10+3)(26+10+3)(2). It's really 34611200 but I left out the [NC] element. But the 3041 that don't end in ".domain.com" would never make it to your domain.

#2 AND IF the request was not for sub.domain.com/accounts/index.php or sub.domain.com/accounts/directory/index.php or ... et cetera, supplying "index.php" from the Rule and "sub.domain.com" from the previously satisfied condition (they go in order, sudden death unless there is an OR)

#3 AND IF the query string is exactly equal to "a=4$"

THEN drop the query string and serve content from sub\.domain.com. Which means sub.domain.com/index.whatever, assuming mod_dir is allowed to do its stuff.

I am aware of the basics and i also am knowledgeable as to the difference between files, folders, rewrites and redirects.

because they are dynamic urls i had to rewrite them first then redirect them

Well, ###. If I'd seen this post before I started answering, I could have saved myself a lot of trouble with the calculator. These two statements simply cannot be reconciled.

ItsDavid




msg:4548872
 3:13 am on Feb 26, 2013 (gmt 0)


Didn't you just get through saying that your ordinary URL has four parameters? Are they each optional?


No i did not mean that my ordinary url has 4 parameters. Each example that i displayed actually displays its own separate page.

so for example i will use the one i am trying to rewrite to the sub.domain.com

index.php?a=4
<<<< this displays its own page and whenever any links on that page are clicked the site generates a whole new url query string and or structure

Then i have this url

index.php?a=28&b=142
<<<<<< this displays its own separate page and the same as the other url if any links on that page are clicked it will do the same and move on to a new page with a completely new query string which could be like the one that gave you the headache lol
index.php?a=11&b=2&c=65&d=3
<<<<<<<< Just to clarify the $ was a typo on my part.

Hopefully that helps to clear up the confusion.


I would like to say thank you for the effort you put forward to try and help me reach my goal.

I would also like to add that i am not going to try and reconcile the two statements however i just want to make it clear that they were in no way a bragging statement or snotty remark. I will clarify.

I am aware of the basics and i also am knowledgeable as to the difference between files, folders, rewrites and redirects.


I made this statement just to let g1smd know that i am aware of the basics of those things listed because he specified.

Be sure you know the difference between a rewrite and a redirect (both are coded from RewriteRules) and be sure you know when you're dealing with URLs (as used on the web) and files and folders (as used inside the server). They are not at all the same thing; they are merely linked by the server configuration.


so i was only making him aware that my knowledge is basic when it comes to rewrites redirects etc.... however i have no knowledge of constructing the correct codes for the rewrites or redirects. No harm intended to anyone.


because they are dynamic urls i had to rewrite them first then redirect them


This second statement was just to clarify that i am aware that with dynamic query string urls you cannot just 301 redirect them you have to first rewrite them then you can 301 redirect the old url to the new rewritten url.


I stated earlier that i am not the best at explaining things and i see that is already working strongly against me here with only 5 posts. But again i just want to say thanks for your efforts.

lucy24




msg:4548896
 5:40 am on Feb 26, 2013 (gmt 0)

This second statement was just to clarify that i am aware that with dynamic query string urls you cannot just 301 redirect them you have to first rewrite them then you can 301 redirect the old url to the new rewritten url.

... and that's the part you've got exactly backward :(

First redirect, if necessary. Then rewrite. Once you've rewritten, you can't do anything more; you need to serve up that content right away before the server forgets where it is.

ItsDavid




msg:4548941
 11:16 am on Feb 26, 2013 (gmt 0)

Well I hate to tell you but with these urls if you 301 them without first creating the rewrite rule for them they lead to a server error file not found because there is no actual file the links are dynamically created.

lucy24




msg:4549203
 9:24 pm on Feb 26, 2013 (gmt 0)

if you 301 them without first creating the rewrite rule for them they lead to a server error file not found because there is no actual file the links are dynamically created

mod_rewrite works on requests. It doesn't care whether the physical file exists or not. And it has no memory.* You can't say "If anyone should ever happen to come along and ask for aaa, send them to bbb which is really ccc." Those are entirely separate rules.

The redirect:

RewriteRule aaa http://www.example.com/bbb [R=301,L]

and the rewrite:

RewriteRule bbb /ccc [L]

If it happens that aaa and ccc are the same, then the redirect needs an accompanying condition that says

RewriteCond %{THE_REQUEST} aaa

do it doesn't go around in circles.

Now, obviously all of those things have to be present in your htaccess file. But mod_rewrite doesn't know that. As far as it's concerned, you can nip in and add the rewrite during that same nanosecond that the redirect is happening. It didn't have to be there earlier.


* Especially within htaccess, where any Regular Expression has to be compiled fresh on every single request. If it's in the config file it may be cached. (I just learned this. It's buried in apache's htaccess documentation. Obviously most of the docs are aimed at the people who own the server, so this isn't a front-and-center detail.)

ItsDavid




msg:4549270
 12:54 am on Feb 27, 2013 (gmt 0)

lucy, I just want to say that i am grateful for the advice thank you.

Any chance you would be able to provide an example of how the rule or rules might have to be setup to work using
index.php?a=4
?
lucy24




msg:4549285
 2:05 am on Feb 27, 2013 (gmt 0)

You'll need to go back a bit and expand.

You said at the outset that
a=4
goes to a subdomain. Additional questions:

Are you setting up a pattern where the user's address bar says "subdomain.example.com" while the content really comes from www.example.com (that is, ahem, the physical directory that resolves to www.example.com) /index.php?a=4 (that is, et cetera, as before). Or is it www.example.com/subdirectory/index.php -- and if so, is it with or without the a=4 part?

Are you dealing with queries containing "a=4" or queries that consist in their entirety of "a=4" ? If there might be other stuff in the query, what do you want to have happen to it? Should it be converted into something in the path of your new URL, or should it stay the way it is?

Do your URLs --the ones seen and used by humans-- currently contain query strings? If no, have they contained them at any time in the past? The second part of the question affects how you handle incoming requests with attached queries.

Do requests for this particular subdomain get sent straight through to some directory that already exists, or do you have to code this part yourself? (Note that "straight through" doesn't mean they teleport directly from the front door of the server to their final destination, bypassing your root-level htaccess. It just means that you don't have to do anything further to help them along.)

ItsDavid




msg:4549304
 3:33 am on Feb 27, 2013 (gmt 0)

Are you setting up a pattern where the user's address bar says "subdomain.example.com" while the content really comes from http:example.com (that is, ahem, the physical directory that resolves to http://example.com) /index.php?a=4
Yes this is correct.


Do your URLs --the ones seen and used by humans-- currently contain query strings?
yes this is also correct i will try to explain it better.

When i user comes to my site and clicks the "Login" link they are taken to the login page with a link displaying in their url as
http://example.com/index.php?a=10
This link dynamically creates the page by making the call to index.php and the following query string. Now once the user logs in they are then redirected to the url and page in question
http://example.com/index.php?a=4
. Every url produces and displays its own page and content by making the call to index.php and then the correct content is displayed based on the query string following index.php so in other words here are a few example links

Home URL >>> index.php

Pricing URL >>> index.php?a=28&b=143

About Us URL >>> index.php?a=28&b=142

Contact Us URL >>> index.php?a=28&b=136

Sell URL >>> index.php?a=1

Accounts URL >>> index.php?a=4

Signin URL >>> index.php?a=10


So as you can see here each url is making the call to index.php then depending on the query string is what page and content it is.

Do your URLs --the ones seen and used by humans-- currently contain query strings?
The urls i have posted above are exactly the way the user's see them in their browser and they are also used by the users.

Do requests for this particular subdomain get sent straight through to some directory that already exists
No there is no directory as each page is dynamically created by making the call to index.php then the query string after index.php determines what content should display on that page. So for example a=4 is the query that pulls up the accounts page and content. Wildcard subdomains are already being used for US regions on my site so what i wanted to do is create a subdomain in cPanel called "accounts" and have "accounts" point to the root domain (same server) at "http://example.com" which is where the index.php file is located and accounts.example.com must get its content from. Unless the rule for index.php?a=4 can be used and rewritten as a wildcard [accounts.domain.com...] without causing any conflict.
lucy24




msg:4549331
 5:27 am on Feb 27, 2013 (gmt 0)

We're not there yet. Remember, Apache is just a stupid computer. It can't make things up; it follows rules to the letter, ending up with either 200 or "Duh, I dunno, I can't find it".

Is "a=4" going to be the entire query string? If yes, you are good to go. If no, you have to figure out what to do with the rest of the query.

Do you want the user to end up with their address bar saying

accounts.example.com/
(and that's all)

or
accounts.example.com/index.php?a=4

or
accounts.example.com/a=4

? The last two both seem pretty pointless but you gotta cover all possibilities.

The redirect half is easy. Assuming the whole query string goes away:

RewriteCond %{THE_REQUEST} [A-Z]{3,9}\ /index\.php\?a=4\ HTTP
RewriteRule ^index\.php http://accounts.example.com/? [R=301,L]

The other half-- the part where their address bar says accounts.example.com while you're feeding them content that lives at www.example.com --is trickier. It depends on how your subdomains are managed. Do the existing subdomains live in directories of their own, or are they too created by throwing parameters at index.php?

If you request a random subdomain-- one that doesn't already exist --where do you end up? How does your htaccess handle the request? Work with your existing rules as much as possible.

g1smd




msg:4549364
 10:22 am on Feb 27, 2013 (gmt 0)

msg:4549363 in thread [webmasterworld.com...] might be useful.
ItsDavid




msg:4549413
 1:07 pm on Feb 27, 2013 (gmt 0)

RewriteCond %{THE_REQUEST} [A-Z]{3,9}\ /index\.php\?a=4\ HTTP
RewriteRule ^index\.php [accounts.example.com...] [R=301,L]
This rule isn't working. If a click the old "index.php?a=4" link it just takes me to the page displaying this original link. Also if i type accounts.example.com directly in my browser it just loads to the home page at example.com I also tried adding the [QSA] flag but that still didn't make a difference.


However i do have this one below which does work and displays the correct page and url of accounts.example.com in my browser but i have to manually type the address because clicking the old url of example.com/index.php?a=4 does not redirect me to the new address. The only problem i have with using this code below is that the only way it works is if i use the [P] flag which i don't want to use because i am reading around the internet that using the [P] flag can be a security risk and that's what leads me on this adventure to discover an alternative way to do this without using the [P] flag.

RewriteCond %{HTTP_HOST} ^(accounts)\.example.com? [NC]
RewriteRule ^$ http://example.com/index.php\?a=4? [R=301,P,QSA,L]



I don't know if this information will help but if i remove the [P] flag from the above code then type accounts.example.com in my browser it redirects to the original url except that it now has %3f at the end but still displays the correct page without any problems
http://example.com/index.php?a=4%3f

[edited by: ItsDavid at 1:20 pm (utc) on Feb 27, 2013]

g1smd




msg:4549414
 1:15 pm on Feb 27, 2013 (gmt 0)

In the final code example...

Escape literal periods in pattern.

Why is accounts in brackets?

Remove P flag.

Remove final question mark on both lines.

ItsDavid




msg:4549421
 1:22 pm on Feb 27, 2013 (gmt 0)

I added the accounts in brackets because i read that it makes it a direct match. I am not sure if that is true but i figured i would try my luck.

g1smd




msg:4549427
 2:02 pm on Feb 27, 2013 (gmt 0)

Brackets are needed either for capturing, or for making parts optional when followed by a question mark.

The %3f on the end was the extra unwanted question mark being added.

[edited by: g1smd at 2:32 pm (utc) on Feb 27, 2013]

ItsDavid




msg:4549429
 2:07 pm on Feb 27, 2013 (gmt 0)

Thanks for the clarification. I made the changes you recommended and it still seems to not work.

g1smd




msg:4549445
 2:32 pm on Feb 27, 2013 (gmt 0)

Define "work" and "not work".

Use example.com in any code to stop the URL auto-linking function.

ItsDavid




msg:4549452
 2:46 pm on Feb 27, 2013 (gmt 0)

Sorry for not being more informal.

What i mean is that when i use this code below with the changes you recommended and the [P] flag removed it no longer works when i type [accounts.example.com...] in my browser instead it redirects to the original url and display page at
http://example.com/index.php?a=4


This is the code that does not work once i remove the [P] flag >>>>
RewriteCond %{HTTP_HOST} ^accounts\.example.com [NC]
RewriteRule ^$ http\://example\.com/index.php\?a=4 [R=301,QSA,L]


i am looking to display accounts.example.com in the browser but it is getting the page and content from
http://example.com/index.php?a=4


When i add the [P] flag back in then type accounts.example.com into my browser it works great meaning displaying accounts.example.com in the browser and displaying the page and content from example.com/index.php?a=4

hope this defines it better.

g1smd




msg:4549459
 2:58 pm on Feb 27, 2013 (gmt 0)

Unfortunately not. The description is ambiguous.

Define in terms of requested URLs (things with http at the beginning) that the user requests, and places inside the server (things without http or hostname) where the content resides.

When user requests X I want to redirect so they request Y.

When user requests Y I want to rewrite the request so the content is internally served from Z.

Again, the target of the redirect is a URL with protocol and hostname (URLs are a reference system used out on the web, not inside the server), and the target of a rewrite is an internal folder and file (protocols and hostnames have no meaning inside the server filesystem).

Here's an example that should already be familiar:

When user requests URL http://www.example.com/index.php I want to redirect user to URL http://www.example.com/

When user requests URL http://www.example.com/ I want to rewrite the request so that content is served from filepath /index.php inside the server.

Mod_rewrite works with requests. It does not make URLs for content. It looks at what the browser requested and either tells browser to make a new request (this is a redirect) or fetches content from inside the server (this is a rewrite).

[edited by: g1smd at 3:04 pm (utc) on Feb 27, 2013]

ItsDavid




msg:4549460
 3:01 pm on Feb 27, 2013 (gmt 0)

If this is of any help this is a code i am using to rewrite some of my links and pages to make them appear as if they are in a directory within the browser. I don't know if it can be better coded for optimization but i am open for suggestions.

I have also tried to tweak this code to get it to work for my sub domain rewrite attempt but it didn't work either.


# Redirect Direct Client Requests For About Us Dynamic URL to Static Equivalent
RewriteCond %{THE_REQUEST} ^a=28&b=142$
RewriteRule ^index\.php$ http://example.com/about? [R=301,L]

RewriteRule ^about$ index.php?a=28&b=142 [L] ## About Us URL

g1smd




msg:4549466
 3:06 pm on Feb 27, 2013 (gmt 0)

The condition
RewriteCond %{THE_REQUEST} ^a=28&b=142$

can never match THE_REQUEST.

THE_REQUEST will be "
GET /index.php?a=28&b=142 HTTP/1.1" or "GET /?a=28&b=142 HTTP/1.1" or similar.
ItsDavid




msg:4549480
 3:44 pm on Feb 27, 2013 (gmt 0)

Define in terms of requested URLs (things with http at the beginning) that the user requests,


when a user requests [accounts.domain.com...] in their browser that is the url i want to display in the browser however the actual page and content is located on the server at http://example.com/index.php?a=4 or in other terms home/user/public_html

I have created a sub domain called "accounts" in cpanel that points to the main site's root where the index.php file is located. the query string needed after index.php is ?a=4 and this is what tells the server this is the page we are requesting. so when put into a URL perspective http://example.com/index.php?a=4 gets the page we are requesting on the server and is where the content is served from.

http://example.com/index.php?a=4 is the real original url to the page on the server so i also need any incoming requests for that url to redirect to [accounts.example.com...] to prevent any duplicate content issues.

g1smd




msg:4549486
 4:01 pm on Feb 27, 2013 (gmt 0)

You had a redirect where you needed a rewrite. Your coded functionality was "exactly backwards" to what you required.


# Redirect
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /(index\.php)?\?a=4\ HTTP/
RewriteRule ^(index\.php)?$ http://accounts.example.com/? [R=301,L]


#Rewrite
RewriteCond %{HTTP_HOST} ^accounts\.example\.com$
RewriteRule ^$ /index.php?a=4 [L]


The redirect will need to be near the beginning of your list of redirects.

The rewrite will need to be near the beginning of your list of rewrites.

If the site uses cookies, make sure they are correctly configured so that they are usable when visitor is on accounts subdomain.

ItsDavid




msg:4549492
 4:18 pm on Feb 27, 2013 (gmt 0)

I think we are getting very close.

when i click the link http://example.com/index.php?a=4 i can see it attempting to load [accounts.example.com...] in the bottom of my browser however my browser redirects to http://example.com

I then tried manually typing in the url [accounts.example.com...] in my browser and that just reloads the page to the site's home http://example.com

This 42 message thread spans 2 pages: 42 ( [1] 2 > >
Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Code, Content, and Presentation / Apache Web Server
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About
© Webmaster World 1996-2014 all rights reserved