Databases
StackOverflow2013
Postsdbo
PO.htaccess route with file check not working with querystring
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO.htaccess route with file check not working with querystring
    primarykey
    data
    text
    <p>I'm certainly no expert with .htaccess files, so bear with me..</p> <p>I have a nice simple rule:</p> <pre><code>RewriteCond %{DOCUMENT_ROOT}/landing-pages/$1.aspx -f RewriteRule ^/(.[^/]*)/?$ /landing-pages/$1.aspx [NC,L,QSA] </code></pre> <p>So if I go to a page: </p> <p><a href="http://myexampledomain.com/my-landing/page/" rel="nofollow">http://myexampledomain.com/my-landing/page/</a> </p> <p>It is rewritten correctly to: </p> <p><a href="http://myexampledomain.com/landing-pages/my-landing-page.aspx" rel="nofollow">http://myexampledomain.com/landing-pages/my-landing-page.aspx</a></p> <p>This works fine, until the original URL has a querystring on it: </p> <p><a href="http://myexampledomain.com/my-landing/page/?foo=bar" rel="nofollow">http://myexampledomain.com/my-landing/page/?foo=bar</a></p> <p>At this point, the rewrite condition isn't met (I assume the querystring is part of $1 ?) and so I get a page not found.</p> <p>I have tried changing my condition to:</p> <pre><code>RewriteCond /landing-pages/%{REQUEST_URI}.aspx -f </code></pre> <p>However, I suspect that %{REQUEST_URI} contains both leading and trailing slashes so that does not work either.</p> <p>Does anyone have any ideas on how I get the condition to ignore the querystring, but still append the querystring in the rule?</p> <p>Any help appreciated.</p> <p>p.s. I know routing is available in .net 3.5+ but currently that is not an option, we are already using .htaccess via Helicon's asapi_rewrite module.</p> <p>Thanks</p> <p>Edit:</p> <p>I have since added another condition and rule to try and narrow down where the problem is:</p> <pre><code>RewriteCond %{QUERY_STRING} foo=bar RewriteRule ^/(.*)/?$ /landing-pages/$1.aspx? [NC,L,QSA] </code></pre> <p>So now this is set to specifically Rewrite if the query string foo=bar exists. Using this I can see that the requested URL after the Rewrite is:</p> <p><a href="http://myexampledomain.com/landing-pages/my-landing-page/?foo=bar.aspx?foo=bar" rel="nofollow">http://myexampledomain.com/landing-pages/my-landing-page/?foo=bar.aspx?foo=bar</a></p> <p>It's certainly not how I expected it to behave..</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMark Johnson
    1. USMark Johnson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO_“I assume the querystring is part of $1 ?”_ – no, it’s not; RewriteRule only matches on the path component of the URL, not the query string. And before we discuss this any further, please edit your posting and format your code in a more readable way.
      singulars
      1. PO.htaccess route with file check not working with querystring
      1. USCBroe
    2. CO@CBroe Apologies, should read a bit better now. I confess to being a little confused as to why the query string should affect my condition then if it's effectively being ignored in my condition? Especially as it appears to work fine if there is no query string. Certainly my initial thoughts were that the query string is a separate entity and so should just be appended to my RewriteRule..
      singulars
      1. PO.htaccess route with file check not working with querystring
      1. USMark Johnson
    3. COOK, I've done an edit to include another RewriteCond which appears to go against how I thought it should work, but my understanding of it is minimal.
      singulars
      1. PO.htaccess route with file check not working with querystring
      1. USMark Johnson
 

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