Closed Bug 198038 Opened 21 years ago Closed 21 years ago

Talkback does not obey proxy username/password settings

Categories

(Core Graveyard :: Talkback Client, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 36545

People

(Reporter: bugzilla, Assigned: mcafee)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

If Mozilla crashes and the talkback agent pops up, it tries to send the data
back. However, it seem to recognise the proxy needs authorisation, so it can't
send data back. There doesn't appear to be anywhere to tell it to authorise.


Reproducible: Always

Steps to Reproduce:
1. Crash mozilla
2. Try to send a talkback from behind a proxy requiring authorisation


Actual Results:  
Talkback complained of a failed connection (because the proxy refused to relay
the request).

Expected Results:  
Successfully sent talkback data.
->mcafee
Assignee: namachi → mcafee
QA Contact: chofmann → namachi

*** This bug has been marked as a duplicate of 36545 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
"WONTFIX"? Is that due to nobody to work on the talkback app, or something else? 
Is the source for the talkback stuff included in Mozilla?


Adding jpatel to confirm this is a dup of 36545, and that it is marked won't fix.
Yes, this is a dup of bug 36545.  And as far as I know, I don't think anyone is
working on authenticating proxy support for the Talkback client.

Shiva:  If you could confirm my thoughts above with a few words in bug 36545
that would be great.  Thanks.
Status: RESOLVED → VERIFIED
>And as far as I know, I don't think anyone is working on authenticating proxy 
>support for the Talkback client.

Like I said, is that purely because of lack of people? Or is the Talkback
component closed-source, so nobody could work on it even if they wanted to? I
didn't see anything which looked immediately talkback-ish during a quick trip
through lxr yesterday.

(Downloading the source tarball is kind of a last resort, it'll take me *ages*.)

If the talkback client is closed, what requirements would a new open one need to
meet to be useful? ie what would it need to record, and how does the existing
client get the information?

Thanks!
talkback source is not, and cannot be released under the MPL.
This is probably a people/time/priority issue.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.