From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-CN; rv:1.2.1) Gecko/20030225
Description of problem:
Something wrong in the "Figure 3-2. HTTP Proxy Configuration".
"For example, to use the proxy server http://squid.mysite.org on port 3128,
enter http://squid.mysite.org:3128 in the text field. "
But actually, the "http://" should not be entered in, otherwise, it would not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Configure the applet as the document text.
Actual Results: Failed
same error exists in the enterprise Document too, please check it.
I'm accepting the bug and blocking the Titan Documentation tracking bug. This
looks like legacy text that contradicts the example in the screenshot itself.
Will be an easy fix.
OK, so this fix wasn't difficult, as expected. But I searched through the User
Guide just to make sure we're consistent and found that we use virtually
identical examples while explaining how to configure an HTTP Proxy for up2date
So I'm changing the status to NEEDINFO and CC'ing Chip, Daniel, and Adrian in
the hopes of ensuring the examples included in the up2date and rhn_register
chapters are indeed accurate. The references I'm requesting review of can be
found in the latest RHN Enterprise User Reference Guide posted on the intranet:
They are on pages 8, 29, and 74. All I need to know is whether or not "http://"
should be included in the HTTP Proxy field. Thanks.
OK, Adrian let me know up2date and rhn_register actually expect "http://" in
that field, so no further changes are needed.
The files are checked into CVS for this. I'm changing status to ON_DEV in
preparation for build -48 at GDK's request.
Looks good in webqa and on -48.
Looks good in prod.