Bug 489602 - mid-air collisions result in security warning
Summary: mid-air collisions result in security warning
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 3.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-10 21:32 UTC by Jeff Bastian
Modified: 2013-06-24 02:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-10 22:21:26 UTC
Embargoed:


Attachments (Terms of Use)
screenshot (108.98 KB, image/png)
2009-03-10 21:37 UTC, Jeff Bastian
no flags Details

Description Jeff Bastian 2009-03-10 21:32:38 UTC
Description of problem:
Occasionally when updating a BZ, I'll get a mid-air collision (usually from pm_ack? being set automatically while I'm adding a comment.  I tell it to just add my new comments to the bug, and then bugzilla tells me (with a big scary red background):
   
   It looks like you didn't come from the right page. One reason could be
   that you entered the URL in the address bar of your web browser directly,
   which should be safe. Another reason could be that you clicked on a URL
   which redirected you here without your consent.

   Are you sure you want to commit these changes?

I click "yes, confirm changes" and everything works, but it shouldn't scare me like that. :)


Version-Release number of selected component (if applicable):
production bugzilla

How reproducible:
every time

Steps to Reproduce:
1. get a mid-air collision
2. tell it to just add new comments

  
Actual results:
security warning

Expected results:
no warning

Additional info:

Comment 1 Jeff Bastian 2009-03-10 21:37:11 UTC
Created attachment 334719 [details]
screenshot

Comment 2 David Lawrence 2009-03-10 22:21:26 UTC
it is a simple html bug where it is not passing your token through the midair screen properly. I have fixed this in svn and will be in the next Bugzilla update.


Note You need to log in before you can comment on or make changes to this bug.