Query String Oddness
Development and Programming
Many of Google’s api’s are dependent upon query string formatting that EE does not appear to be tolerant of. I’m curious how people are working around this.
A little background - I have removed “index.php” with mod_rewrite and, therefore, am not forcing query strings.
Strangely, passing a single parameter in a query string causes a 404. Example: example.com/products/music/?info=foo
Passing more than one parameter separated by the ampersand DOES NOT cause a 404. Example: example.com/products/music/?info=foo&more=bar
I’m just hoping to hear how the rest of you are working with traditional query strings in an EE site.
Can you post the index.php rewriting portion of your .htaccess file and what it the $config[‘uri_protocal’] set to in your system/expressionengine/config/config.php file? Assuming you are on EE2.
Yep, I’m using EE2.
.htaccess:
RewriteCond %{REQUEST_URI} !(.[a-zA-Z0-9]{1,5})$ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteCond $1 !^(experience|partners|preview|industry|images|system|themes|public|sIFR|favicon.ico|robots.txt|index.php) [NC] RewriteRule ^(.*)$ /index.php/$1 [L]
config.php:
$config[‘uri_protocol’] = ‘AUTO’;
Thanks
the3mus1can, per your question, I changed uri_protocol to ‘PATH_INFO’ and it seems to correct the “issue” on my local apache server. Can you shed some light on this?
If you do:
echo '<pre>';
var_dump($_SERVER);
echo '</pre>
<p>’;You can see where the different uri_protocols are looking for the data. Whether or not you can use REQUEST_URI or PATH_INFO or AUTO is largely dependent on your server configuration.