Closed Bug 530708 Opened 16 years ago Closed 16 years ago

Socorro UI - Disallowed key characters in global data.

Categories

(Socorro :: General, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lars, Assigned: ozten)

Details

when attempting to drill down from a search page to a list of crashes, I get a page that says: "Disallowed key characters in global data." and nothing more. reproduced with this URL: https://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox:3.5.5&query_search=signature&query_type=exact&query=&date=&range_value=1&range_unit=weeks&do_query=1&signature=nsCOMPtr_base::assign_from_qi%28nsQueryInterface,%20nsID%20const&%29&page=1
Can you list exact repro steps? The url above isn't url encoded properly. It should look like: https://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox:3.5.5&query_search=signature&query_type=exact&query=&date=&range_value=1&range_unit=weeks&do_query=1&signature=nsCOMPtr_base%3A%3Aassign_from_qi(nsQueryInterface%2C%20nsID%20const%26)&page=1 I did the following and was unable to repro your issue: 1) Got to homepage 2) Search product=Firefox version=3.5.5, adv search exact signature=nsCOMPtr_base::assign_from_qi(nsQueryInterface, nsID const&) 3) Click Filter button 4) Click only link in query results 5) Viewing report/list - seeing all crashes
eh, I think we've lost it. I just did a simple query for FF3.5.5. In the query results, at about position 95, I found the signature I needed and clicked on it. That's when I got the "Disallowed..." message. I clicked the back button, and right clicked the offending link and saved the link destination to the clipboard. I pasted it directly into the url line and got the same "Disallowed..." message. I clicked on several other links from the original search results and found them working properly. I then wrote the bug report, and pasted the offending url into the report. I am not now able to reproduce this problem.
Yes! I've figure this issue out. It only happends if your logged in and on a non-secure page. The query string parameters weren't getting encoded properly for the path we use to do the secure redirect. Repro'd in stage and verified the fix. r1555.
Assignee: nobody → ozten.bugs
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.2
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.