Fossil

View Ticket
Login

View Ticket

2010-08-26
11:31 Fixed ticket [311fbfd6b6]: Unable to "fossil conf pull all" via proxy plus 1 other change ... (artifact: 147029b13f user: drh)
11:31
Enable proxy handling for "config push" and "config pull" Tickets [0d1a4fe14f1fb6ee2082] and [311fbfd6b696142a4b2c86dc]. ... (check-in: 1a9fe88b66 user: drh tags: trunk)
07:32 Ticket [311fbfd6b6] Unable to "fossil conf pull all" via proxy status still Open with 2 other changes ... (artifact: 0e6fd3c129 user: anonymous)
2010-08-24
13:07 New ticket [311fbfd6b6]. ... (artifact: 59a36d1f93 user: anonymous)

Ticket Hash: 311fbfd6b696142a4b2c86dcf2c4595ed3e5a0ed
Title: Unable to "fossil conf pull all" via proxy
Status: Fixed Type: Code_Defect
Severity: Important Priority:
Subsystem: Resolution: Fixed
Last Modified: 2010-08-26 11:31:55
Version Found In: [8474ca6747] 2010-08-23 22:24:16 UTC
Description:
C:\foo>fossil pull
Server:    http://user@example.com/repo/foo.repo
via proxy: http://192.168.2.1:3128/
                Bytes      Cards  Artifacts     Deltas
Send:             146          2          0          0
Received:         384          9          0          0
Total network traffic: 370 bytes sent, 438 bytes received
same local repository, same remote repository url and proxy settins, user has admin privileges:
>C:\foo>fossil conf pull all
                Bytes      Cards  Artifacts     Deltas
Send:             619         24          0          0
fossil: can't resolve host name: example.com
It turns out that fossil conf do not respect proxy setting at all. Should this be fixed or it is intentional?

anonymous claiming to be urmil added on 2010-08-26 07:32:27:
Duplicate of [0d1a4fe14f]. See that ticket for fix.