Closed
Bug 134050
Opened 24 years ago
Closed 24 years ago
the return receipts we send out don't have our user agent
Categories
(MailNews Core :: Backend, defect, P2)
Tracking
(Not tracked)
VERIFIED
INVALID
mozilla1.0
People
(Reporter: sspitzer, Assigned: jt95070)
References
(Blocks 1 open bug)
Details
(Whiteboard: [adt2])
the return receipts we send out don't have our user agent.
my guess is that they should.
Updated•24 years ago
|
Yes, we do. We package it into the "Reporting-UA:" header based on the spec.
Below are sections of code from nsMsgMdnGenerator.cpp.
...
nsCOMPtr<nsIHttpProtocolHandler> pHTTPHandler =
do_GetService(NS_NETWORK_PROTOCOL_CONTRACTID_PREFIX "http", &rv);
if (NS_SUCCEEDED(rv) && pHTTPHandler)
{
nsCAutoString userAgentString;
pHTTPHandler->GetUserAgent(userAgentString);
if (!userAgentString.IsEmpty())
{
tmpBuffer = PR_smprintf("Reporting-UA: %s" CRLF,
userAgentString.get());
PUSH_N_FREE_STRING(tmpBuffer);
}
}
...
this what I see in my return receipt using Seth's windows build:
Reporting-UA: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.9+)
Gecko/20020325
It's the first line in 2nd part (Mdn part2.txt)of return receipt..
Seth, I am marking this as invalid since we do have the user agent information
added to the Reporting-UA: header instead of X-Mailer: header.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Verified - we have Reporting-UA: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.2a) Gecko/20020910
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•