Bad Request - Firefox & Chrome - Google Analytics

I'm having a problem with a Google Analytics Tracking cookie. When users click off a promotional email we send out the site will load fine, but if they click off the initial page that was loaded they get a "Bad Request" message and the server logs a 400 status code.  This only happens in Firefox and Chrome.  IE works fine. If you clear out the __umtz cookie  (which is set by Google Analytics) in your browser the page and site will load fine. I pretty sure I've reached the end of the internet googling this problem but can't figure it out.  
Nex-TechAsked:
Who is Participating?
 
jeremyjared74Commented:
It might be helpful to have a link to the error.
0
 
Nex-TechAuthor Commented:
a link to the error? what are you talking about?  Its a 400 Bad request error.  It gets generated by the browser...
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
jeremyjared74Commented:
Maybe if you re-write the question it would make more sense. I don't understand your question. This is probably why no-one has posted here yet.

The link is in an e-mail? I am trying to help, but I must understand your question.
0
 
Nex-TechAuthor Commented:
ok here is the link from the email

http://app.bronto.com/public/?q=ulink&fn=Link&ssid=14561&id=e5qh9lv82rbnhs19kbhvusazsa8qb&id2=7fy42z2s8582yzxbomstddrlowrcd&subscriber_id=bsspjtpbjdzjtegegsfhnblnzoenbkn&delivery_id=bwevblbpkmwbirrnyowwprudgeypbfg&tid=3.OOE.BYe0HQ.Bwyv.Nvgu..P2XU.b..l.A2CS.a.TJd28A.TJeCPQ.kFSm8g

Our email service provider does link tracking and conversion tracking so they rewrite our orginal url so they can drop a cookie.  Now you notice the page loads fine, but if you click anywhere else on the site, say the logo at the top, you get a bad request.  I troubleshooted by going and deleting individual coookies until the site would reload.  I found that the __umtz cookie, which is associated with Google Analytics was the cookie causing the problem, but I am unsure of why as it has never caused a problem before.  Again, this only occurs in Firefox and chrome (i havent tested opera or safari) but IE works fine amazingly.
0
 
jeremyjared74Commented:
OK, that will help. I opened the site in SeaMonkey which has some good web tools. It has an error reporting function that I used to view your errors with. I am sending a file and the error description. It is a good place to start. I need to look at it a little better to find the error causing the 400 error.

I am going to be busy for the next couple hours, but I will look at it as soon as I can. I will post when or if I find your solution.

errors.txt
the-file.txt
0
 
Nex-TechAuthor Commented:
Thanks.  I'll try and go through the those logs a little more in depth.  Scriptresource is generated by .NET. I wouldn't think that would be causing the error though.
0
 
tylermirandaCommented:
Did you ever find anything out jeremyjared74?  I think the scriptresource error is being generated because I am gzipping axd files.  I feel like it might be something with the cookie header length maybe?
0
 
jeremyjared74Commented:
No, I am just now finishing up some work for a website I am designing. I will be free in about 30 minutes, and I will look at it. Sorry it is taking so long.
0
 
tylermirandaCommented:
no worries.  Thanks.  I'm just out of ideas, lol.
0
 
jeremyjared74Commented:
OK, I found a person that was having the same error as you. I don't know if this is causing the Bad Request or not. If you understand the fix, I would try it and go from there. I will look some more for other problems.
0
 
jeremyjared74Commented:
OK, I think I figured it out. It is the + sign that Firefox doesn't like. I figured it out by following your link, and copying the URL from the address bar, then pasted it into Notepad ++. If you do that, you will see that the + sign is being converted to jumbled text in Firefox. Pick a redirect URL without the + and you should be good to go.
0
 
tylermirandaCommented:
That goes along with what I have been thinking, I'll try a few different things and report back.
0
 
tylermirandaCommented:
ah ha!  thats makes perfect sense!
0
 
tylermirandaCommented:
one other thing....Ok I see now that this causes the problem, but how do I fix.  I'm using UTF-8 encoding on the server so that shouldn't be the problem.
0
 
jeremyjared74Commented:
The encoding doesn't matter in the URL. I don't know why Firefox has trouble with it. Usually it is IE that has the issues.
0
All Courses

From novice to tech pro — start learning today.