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.

Url Parameters: Using only 1 always causes a 404

October 14, 2010 11:48am

Subscribe [6]
  • #1 / Oct 14, 2010 11:48am

    WDBookassist

    26 posts

    Hello all:

    Strange issue here maybe someone recognises. I tried doing searching but nothing came up, which was surprising given how common I’d imagine something like this is.

    First up I’m using EE v2.1.0 and primarily the Pages modules, although the same behaviour is happening on normal channel-based paths as well.

    If I append any single URL parameter onto any URL in the site, I get a “Status: 404 Page Not Found.”

    <a href="http://www.example.com/?x=1">http://www.example.com/?x=1</a>

    We are using a few non-EE bits of PHP for external feeds that pass an URL parameter. We also have tracking system where a parameter is appended to URLs. Also google pay-per-click appends a tracking code and I’m worried about this happening in that case. It seems like a fairly innocuous requirement that if the appended parameter doesn’t interfere with CMS variables it shouldn’t cause an issue? (This was always okay on EE 1.x)

    One weird fix I’ve found it that appending 2 parameters fixes the problem, and delivers the page with parameters intact!

    <a href="http://www.example.com/?x=1&y=2">http://www.example.com/?x=1&y=2</a>

    Can anyone shed some light on this and possible solutions?

    Update: I just noticed the 2 parameter fix only works on sub-pages. It does not work on the root page of the site.

  • #2 / Oct 14, 2010 3:53pm

    Ingmar

    29245 posts

    What version and build of EE are you using? Are you removing index.php from your URLs with mod_rewrite?

  • #3 / Oct 15, 2010 11:02am

    WDBookassist

    26 posts

    I am using ExpressionEngine is v2.1.0 Build 20100810.

    Are you removing index.php from your URLs with mod_rewrite?

    I am, as it happens. But renaming (thus disabling) my .htaccess file does not change the behaviour. Once I’ve put in the path with index.php, appending a single parameter still returns 404. Is there something else I’d have to do?

  • #4 / Oct 15, 2010 4:49pm

    Sue Crocker

    26054 posts

    Hi, Pierce. I can replicate the problem you’re having, but as you said .htaccess isn’t a factor in this case. I’m going to be posting this to the devs to see if there is something we can do about it. Thanks in advance for your patience.

  • #5 / Oct 15, 2010 4:54pm

    mcleand

    1 posts

    I am having the same problem. So that when a click thru from google adwords thus

    http://onlineone.com.au/index.php/services/implementing-netsuite?gclid=CJDjr_LP1aQCFQRCbgodn

    ends up with the 404 page.

  • #6 / Oct 16, 2010 11:45am

    Sue Crocker

    26054 posts

    Thanks for adding your scenario, mcleand. This should help the devs in figuring out what the issue is. Thanks in advance for your patience.

  • #7 / Oct 19, 2010 10:11am

    WDBookassist

    26 posts

    Thanks Sue. I look forward to hearing back about this.

  • #8 / Oct 19, 2010 3:45pm

    Ingmar

    29245 posts

    Just keep us in the loop, please.

  • #9 / Jan 10, 2011 12:23pm

    GlobalGraphics

    36 posts

    We have had a similar problem on our website. We have contacted Google and had this response:

    Thanks for your call. Following our conversation, I have now included some
    information about auto-tagging, how it is affecting your site and what
    action needs to be taken to resolve the issues you are experiencing.

    ***Auto-tagging***

    I understand that after activating Analytics within your AdWords account,
    your ads have been directing visitors to an error page. When Analytics is
    activated within AdWords, ‘Destination URL auto-tagging’ is automatically
    turned on. This feature allows Analytics to track information about clicks
    on your AdWords ads by tagging your AdWords keyword Destination URLs with
    a ‘gclid=’ parameter. This parameter is displayed in your landing page
    URL. Some websites do not allow URL parameters and serve an error page as
    a result.


    ***Your site***

    While reviewing your website, I found that a your site does not allow
    these tracking parameters and is sending visitors to a 404 error page.

    To prevent this occurring I showed you how to turn off auto-tagging in
    your account. Your ads are no longer going to error pages as a result.

    However, without Auto-tagging turned on Analytics is unable to track
    visitors reaching your site through AdWords properly.

    I recommend contacting your webmaster to request that they change the
    website so that it allows Tracking Parameters. If this isn’t possible you
    will not be able to use AdWords and Analytics together.


    I hope this information is helpful. Do let me know if you have any further
    related queries or concerns and I will be more than happy to address them.

    Hope that helps a little.

  • #10 / Jan 10, 2011 4:35pm

    Ingmar

    29245 posts

    Thank you, GlobalGraphics. Does that mean you were able to solved it, or do you still require assistance?

  • #11 / Jan 11, 2011 4:47am

    GlobalGraphics

    36 posts

    We couldn’t solve it. Currently our Auto Tagging is off.

  • #12 / Jan 11, 2011 3:57pm

    Ingmar

    29245 posts

    And that’s working for you, I understand? Just let us know if and when you want to revisit the issue. Thanks.

  • #13 / Feb 03, 2011 8:44pm

    Jack Tse

    67 posts

    Hi - This is an issue for me as well. Our client is using a marketing company that has proprietary software that appends tracking code to it as well.

    Is there a way to do this via a server rewrite or something? Thanks!

  • #14 / Feb 04, 2011 11:26am

    Sue Crocker

    26054 posts

    Hi, Jack. Did you see the post earlier about turning on force query strings? Did that help?

  • #15 / Feb 11, 2011 7:52am

    WDBookassist

    26 posts

    Hi, I am still experiencing this problem, as described above. It’s continuing to cause issues with integrated codes for tracking, etc. Basically anything I’ve tried to use that automatically appends a single url parameters.

    Any updates on whether a fix is being explored?

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

ExpressionEngine News!

#eecms, #events, #releases