19271 - talkback proxy settings don't work

Status: RESOLVED INVALID

(Core Graveyard :: Talkback Client, defect, P3)

Description

[matt wilkie]

Hi, this is my first bugzilla attempt so please don't flame(broil) me, a light
 scorching will suffice if it is informative.I did locate any relevant bugs
searching for "talkback" in the summary and description fields.

The Talkback Agent does not seem to be able to go through our firewall. Is there
some other way I can send the data it collects?

The proxy settings I've tried are (the 1st line is what works in Mozilla):

"firewall.gov.yk.ca" "80"
"http://firewall.gov.yk.ca" "80"
"199.bla.bla.bla" "80"

SOCKS is unchecked because I don't know if it works or not. I did try the same
settings as HTTP tho'.

-matt

Comment 1

[matt wilkie]

Attachment: proxy settings for talkback &mozilla

Comment 2

[chris hofmann]

-> namachi

Comment 3

[Shiva Thirumazhusai]

Using the Quality Feedback Agent with Automatic Proxy Configuration

If you are using automatic proxy configuration, and you want to use the Full
Circle Talkback Quality Feedback Agent to send incident reports to Netscape, you
need to replace the talkback.ini file with one that contains the appropriate
Proxy configuration
information:

     1.  If you are using an HTTP proxy, or both an HTTP and SOCKS proxy, create
a file named talkback.ini, containing these three lines, using your proxy host
name, domain, and port:

          UseUserHTTPProxyInfo=1
          UserHTTPProxyHost="yourproxy.yourdomain.com" UserHTTPProxyPort=xxxx

        If you are using a SOCKS Proxy, create a file with these three lines:
          UseUserSOCKSInfo=1
          UserSOCKSHost="yourproxy.yourdomain.com"
          UserSOCKSPort=xxxx

     2. Replace the existing talkback.ini file with the version you created.

     On Windows 95 and Windows NT systems, copy the talkback.ini file to this
location, in the directory containing
     Netscape.exe:
     \Fullsoft\data\talkback.ini

Comment 4

[matt wilkie]

I found Talkback.exe in two places, but only one .ini. It didn't make any
difference which executable I ran. I tried both with and without socks.

Directory of C:\local\mozilla\bin 09/29/99 08:51a 1,419 talkback.cnt 09/29/99
08:51a 357,376 talkback.exe 09/29/99 08:51a 32,960 talkback.hlp
Directory of C:\local\mozilla\bin\components 11/15/99 09:50p 1,419 talkback.cnt
11/15/99 09:50p 357,376 talkback.exe 11/15/99 09:50p 32,960 talkback.hlp
Directory of C:\local\mozilla\bin\components\Netscape\Communicator5.0 11/19/99
10:49a 630 Talkback.ini

 ---<TALKBACK.INI >---
UseUserHTTPProxyInfo = 1 UserHTTPProxyHost = "firewall.gov.yk.ca"
UserHTTPProxyPort = 80 UseUserSOCKSInfo = 0 UserSOCKSHost = "firewall.gov.yk.ca"
UserSOCKSPort = 1080 HistorySettings = 3, 10, 100 SeenIntro = 1 WantUpdates = 0
UserEmailAddress = "[e-mail]" SupportID = MainWindowTop = 269
MainWindowLeft = 516 MainWindowWidth = 679 MainWindowHeight = 327 ColumnWidths =
80, 90, 115, 150 RandomPool =
ADC1BE717EADB5348C88B2F60A17C3BA8B8F4060AF6775585980BAE778E0279C2ACAE9B6D138AC519042BFDCA79C66FD095C0BE50F2BE0C49BE584AF18F0787B1E2DB2B7E2566641CC1C5483668685E188BC905DEDAAEF676EE01AD84339178F7C9D52684F92D20603E1383CA6A6927BFC04549D7F4BC5E578305E34E869EDA4
LocalKey = 9D756942D8
----------

Comment 5

[matt wilkie]

sorry about the formatting of that last comment, they were all seperate lines
originally in the form.

Comment 6

[matt wilkie]

I don't know why, I didn't change anything, but this morning talkback worked
after a crash.

There is a curiosity though, the first 2 reports which were in the queue on
friday are gone. The third, from this morning, is there and marked 'Sent'. I'm
not going to change the bug's status flag to 'works for me' until another report
is sent successfully.

Oh, one more note: SOCKS are -not- supported by our firewall.

Comment 7

[matt wilkie]

crashed Moz purposely in order to test Talkback proxy settings; it worked again
so I've marked this bug "works for me". /matt

Comment 8

[leger]

Sound good.  Marking Verified.

Comment 9

[matt wilkie]

M13: Talkback doesn't work "out of the box". The bug is that the proxy settings 
via the user dialog doesn't work. The workaround is to manually edit the 
Talkback.ini file as mentioned previously. On my system the .ini is located in:

%mozdir%\bin\components\Netscape\Communicator5.0

Comment 10

[leger]

Clearing WORKSFORME resolution due to reopen.

Comment 11

[Michael R. Eckhoff]

Talkback also doesn't address people with HTTP Auth proxies.  I have a couple 
of bugs from today's release (3/8/2000) that are in the queue that I'd like to 
send it.

Is there a manual process to send it?

Comment 12

[Shiva Thirumazhusai]

How long it is pending in the queue ? 

Comment 13

[Michael R. Eckhoff]

It isn't now.  I found that I had been running 20000305 release and needed to
update to 030908 to fix another bug that impacted me more.  If I crash again,
i'll see what happens.

The bug that crashed me in the 0305 release didn't show up in the new release so
it is no major loss.

Either way, the talkback software didn't have a field for 'username' and
'password' so it can't work with an auth proxy server even if I did still have
things in the queue.

-me

Comment 14

[Paul Newman]

Maybe only in proxy servers where you have to input a user name and password 
(like MS proxy 2.0) - there' nowhere in talkback to input proxy user id and 
password. Anyway, I have this problem too.

Comment 15

[Shiva Thirumazhusai]

Moved to talkback component.

Comment 16

[Dawn Endico]

leger is no longer @netscape.com
changing qa contact to default for this component

Comment 17

[[e-mail]]

How important is this for data gathering? I added Lisa Chiang because she is
probably a big stakeholder in any data that is being lost.

I have seen some strange talkback errors on my Mac regarding proxy, so this type
of problem concerns me.

[e-mail]: are the instructions you provided here posted in some
public location?

If possible, it would be best for the limitations of proxy support in talkback
to be documented in one central location.

Here's a generic set of proxy tests that should be run against talkback. If
someone needs access to a proxy server to work on this bug, please contact me.

http://www.packetgram.com/pktg/proxy/genericproxytest.html

Comment 18

[Shiva Thirumazhusai]

--->[e-mail]

Comment 19

[Edson Carlos Ericksson Richter]

The talkback proxy settings are not working or talkback just does not work with 
authenticated proxy (trought HTTP BASIC AUTH)?

Comment 20

[David Cox]

I am also behind a Squid proxy-caching web server with authorization enabled. It
would be very nice to have talkback working this configuration, even though the
nu,bers of crashes have reduced markedly in the last few months.

Comment 21

[benc]

+nsenterprise - ~20% of all public web traffic comes through a proxy. If we want
to  track crashers, we need to fix this.

David: if you thing auth should work, please create an new bug and mark the
severity as enhancement.

Comment 22

[Hong Kwon]

marking nsenterprise-; will be reevaluated for nsenterprise in future release.

Comment 23

[Sobrinho]

Attachment: don´t work for me

as mentioned previously in comment #3
http://bugzilla.mozilla.org/show_bug.cgi?id=19271#c3

I manually edit the Talkback.ini file 


I found 'Talkback.ini' in two places
C:\Arquivos de programas\mozilla.org\Mozilla\components\Netscape\Gecko1.0
and 
C:\Arquivos de programas\mozilla.org\Mozilla\components\Netscape\MozillaTrunk

I edit and now my file is
UseUserHTTPProxyInfo=1
UserHTTPProxyHost="10.0.1.112"
UserHTTPProxyPort=3128

and don't work

Comment 24

[Sobrinho]

sorry, win98, build 2002082109

Comment 25

[Jan Carpenter]

jay is working with the proxy issues, reassigning to him.

Comment 26

[Jay Patel [:jay]]

Changing QA contact to namachi...

I'm currently testing the Talkback Client proxy settings.  As soon as we find
out what the problem is/might be I will update this bug.

Sobrinho:  Are you still having problems with the latest MozillaTrunk builds?  I
don't think you need to edit the talkback.ini anymore...but you might experience
some problems with authenticating proxies (since Talkback does not support
username/passwords for the proxy settings).  Please try again if possible and
update the bug with your information (what kind of proxy, what kind of
connection, etc).  Thanks.

Comment 27

[Sobrinho]

Jay Patel,
>but you might experience
>some problems with authenticating proxies 
yes, I have problemas with authenticating proxies 

>(since Talkback does not support
>username/passwords for the proxy settings)
sorry, I don't knew about this
;-)

Sobrinho

Comment 28

[Jay Patel [:jay]]

Sobrinho and Michael R. Eckhoff: From looking at other proxy related bugs, I
found a workaround (I haven't tried myself, but you might want to look into it).  

From bug 36545:
------- Additional Comment #5 From Steve Chapel 2000-11-28 14:50 -------

A workaround on the PC platform is to use Proxomitron
http://members.tripod.com/Proxomitron/

You can follow the instructions given here
http://setiathome.berkeley.edu/faq.html#q49 to set it up for authenticating
proxies. Assuming that you're running Proxomitron on port 8080, you can then
configure Talkback to use localhost:8080 as the HTTP proxy, and Proxomitron will
add the user and password information automatically.

-----------------------------------------------------------------------------
Try that out and see if it works.  The comment was submitted a while back, so
not even sure if proxomitron is still around or not.

Comment 29

[Renato Coutinho]

*** Bug 178136 has been marked as a duplicate of this bug. ***

Comment 30

[J.Smith]

The suggested 'workaround' of using 'Proxomitron', is only valid on Ms-Windows. 
The executable only runs on this platform. (By the way, a current URL is 
http://www.proxomitron.org ). But this does nothing for users of other 
Operating Systems, like Linux/BDS/Mac/etc. 

The problem I am personally experiencing with talkback, is that it doesn't work 
with authenticating proxy's that ask for userid/password, like the iPlanet 
proxy 3.6 that Im using.

Comment 31

[steve common]

SC In my case, problem is due to non/mis-handling of proxy authentification
dialogue by talkback. I have no difficulties at home when going through my own,
local transparent proxy (no authentification dialogue is used).

Comment 32

[steve common]

Doh! Talking of proxies, ours had "eaten" the last part of this page and so I
didn't see the workaround :-(

Comment 33

[Maarten Geurts]

It down´t really tell what goes wrong. 
Does it do automattically proxy connects?
Does it support the new ntlm proxy´s (win32 only) as in bug 159015 (ntlm works
in 1.4 )

Comment 34

[Jo Hermans]

*** Bug 217659 has been marked as a duplicate of this bug. ***

Comment 35

[Uri Bernstein]

*** Bug 267128 has been marked as a duplicate of this bug. ***

Comment 36

[OstGote!]

Note that talkback does not function with authenticating proxies, see Bug 36545.
Is there any difference to that bug? Are the problems only with auth proxies?

Comment 37

[benc]

I'm confused about the exact problem.

The original bug, as I understood it, was that manual settings to a normal
(non-authenticating) proxy worked. But PAC users were stuck because talkback
can't understand PAC (no JS interpreter). So the instructions provided were for
manually hacking a single server config.

On my Mac, right now, I see a checkbox for PAC, but I don't understand how it
works (does it use the OS setting? or the profile setting?)

Comment 38

[Jo Hermans]

*** Bug 279777 has been marked as a duplicate of this bug. ***

Comment 39

[Jo Hermans]

*** Bug 293446 has been marked as a duplicate of this bug. ***

Comment 40

[Adam Guthrie]

*** Bug 306554 has been marked as a duplicate of this bug. ***

Comment 41

[Adam Guthrie]

*** Bug 306552 has been marked as a duplicate of this bug. ***

Comment 42

[Jo Hermans]

*** Bug 323948 has been marked as a duplicate of this bug. ***

Comment 43

[Zarco Zwier]

I'm have the same problem with our firewall/proxy as the poster.
We're using a proxy with authentication.
When connection with Firefox, I get a authentication pop up, but when using the Talkback Client, I don't.
Does the Talkback Client share code for proxies with the browser?

Comment 45

[Serge Gautherie (:sgautherie)]

Talkback isn't used anymore:
R.Invalid now.

Comment 46

[BMO Automation]

Attachment: GitHub Pull Request