Bug 489602

Summary: mid-air collisions result in security warning
Product: [Community] Bugzilla Reporter: Jeff Bastian <jbastian>
Component: Creating/Changing BugsAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2CC: dkl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-10 22:21:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

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.