ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Forced Query Strings Not Ideal - Why?

April 22, 2008 12:21am

Subscribe [3]
  • #1 / Apr 22, 2008 12:21am

    jtree

    255 posts

    I use Dreamhost and as far as I can tell they don’t support the “path_info” variable, which means I have to use the “Force Query String” setting in EE.  In this knowledge base article it says Forced Query Strings aren’t ideal but can someone explain to me why it’s not ideal?  Are there any drawbacks to running a site that way?  Thanks!

  • #2 / Apr 22, 2008 1:00am

    Arun S.

    792 posts

    I think the author of that kb article just means that it’s not the first choice in a default EE install.  From my understanding, the only drawback is pure aesthetics.  I’ve been running a site on a server (well, was…finally convinced the client to switch hosts but not for anything related to query strings) that didn’t have URL segment support.  Everything seems to work as it should.  I used .htaccess to remove the index.php? anyway so it ended up not mattering one bit.

  • #3 / Jun 09, 2008 2:49am

    setheryb

    39 posts

    Could you show the htaccess code you used to remove the index.php?  from the address?  Is it the same code used to take out index.php but with the “?” added to it?

  • #4 / Jun 09, 2008 7:44am

    Arun S.

    792 posts

    Is it the same code used to take out index.php but with the “?” added to it?

    Yes, exactly.  I used the .htaccess instructions in the related wiki article but added a “?” to the end of the redirect directive.

    For the site in question, I used the “include” method (instructions in that wiki article), but I don’t think that is relevant to this working.

    HTH

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases