Bug 75 - Bugzilla adds info about Firefox in each bug report
Summary: Bugzilla adds info about Firefox in each bug report
Status: RESOLVED FIXED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-17 05:17 CET by Ahmad Samir
Modified: 2014-05-08 18:05 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ahmad Samir 2011-02-17 05:17:32 CET
In some bug reports we get info about Firefox in the report, e.g.:
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12pre) Gecko/20110214
Firefox/4.0b12pre
Build Identifier: 

This is not needed in for our uses.
Comment 1 Michael Scherer 2011-02-17 09:12:34 CET
Can you giva a exemple of bug report, and where you see this ?

CC: (none) => misc

Comment 2 Oliver Burger 2011-02-17 09:18:51 CET
Here for example:

https://bugs.mageia.org/show_bug.cgi?id=29

CC: (none) => oliver.bgr

Comment 3 Michael Scherer 2011-02-17 09:42:35 CET
It occurs only with firefox ? No specific extension ? 
my own guess is that there is something that mess with the Header at http level that cause the problem.
Comment 4 Oliver Burger 2011-02-17 09:47:26 CET
In my example it was chromium, but Ahmad was writing about FF-4.0.

Oliver
Comment 5 Michael Scherer 2011-02-17 09:52:59 CET
Ok, and does it occurs every time ?
( ie, can we reproduce it easily ? )
Comment 6 Oliver Burger 2011-02-17 09:55:32 CET
Don't know. Would have to create a new bug report for that...

Oliver
Comment 7 Nicolas Vigier 2011-02-17 11:44:06 CET
(In reply to comment #5)
> Ok, and does it occurs every time ?
> ( ie, can we reproduce it easily ? )

It seems to occur most of the time, but there are a few exceptions.

CC: (none) => boklm

Ahmad Samir 2011-02-18 03:02:13 CET

CC: (none) => LpSolit

Comment 8 Frank Griffin 2011-02-18 14:03:04 CET
Can we get a wireshark (or other sniffer) trace of the HTTP request that is sent ?

CC: (none) => ftg

Comment 9 Frank Griffin 2011-02-18 14:18:59 CET
Since the demarcation between the HTTP header and the body is a double newline, the most likely cause is that the value for the header preceding "User-Agent:" has an embedded newline at the end.
Comment 10 Michael Scherer 2011-02-18 14:29:23 CET
Wireshark would likely be useless, as we are using ssl. But someone could use stunnel to simulate a cleartext bugzilla and therefor sniff it. Other possibility, LiveHTTPHeader extension. 

And in the trace, do not forget to check to not add password :)
Comment 11 Frédéric "LpSolit" Buclin 2011-02-18 16:46:34 CET
(In reply to comment #0)
> In some bug reports we get info about Firefox in the report, e.g.:
> User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12pre) Gecko/20110214
> Firefox/4.0b12pre
> Build Identifier: 

When you use the guided form to file bugs (which is the default for this installation), the User-Agent and the Build Identifier are automatically added to the bug comment. To remove them, remove these two lines from
template/en/default/bug/create/comment-guided.txt.tmpl:

 User-Agent:       [%+ cgi.user_agent() %]
 Build Identifier: [%+ cgi.param("buildid") %]
Comment 12 Frank Griffin 2011-02-18 20:03:23 CET
(In reply to comment #11)

> When you use the guided form to file bugs (which is the default for this
> installation), the User-Agent and the Build Identifier are automatically added
> to the bug comment. To remove them, remove these two lines from
> template/en/default/bug/create/comment-guided.txt.tmpl:
> 
>  User-Agent:       [%+ cgi.user_agent() %]
>  Build Identifier: [%+ cgi.param("buildid") %]

Are you saying that these lines are intentionally added to the *body* of the request ?  Or are they intended to be added to the request *header* ?

In the former case, the observed behavior is intentional (and can be corrected by the directions you gave).  In the latter case, there is a bug - either the header preceding "User Agent:" has an unwanted newline at the end of its data portion (resulting in a double-newline which terminates the header section), or else some other code is adding the extra newline before "UserAgent:".
Comment 13 Frédéric "LpSolit" Buclin 2011-02-18 20:06:13 CET
(In reply to comment #12)
> Are you saying that these lines are intentionally added to the *body* of the
> request ?

body, yes.
Comment 14 D Morgan 2011-02-18 21:26:18 CET
thank you again Frédéric, i just modified our templates tks to your help.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Nicolas Vigier 2014-05-08 18:05:41 CEST

CC: boklm => (none)


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