TOPIC:

Hi
From where I have installed CT, I access to internet through a proxy.
My internet browser is configured as expected and works fine.
But downloads from CT don't : can I configure proxy parameters for CT ? Where ?

Thanks

Sir, please look here

Ok, it works for me.

Because I didn't found this easily, I describes how I did it on Windows :

- create a text .ini file containing :The syntax is not exactly the same as in Firefox or Internet Explorer, and not well documented in wget help :

• we must know that CT is using http protocol, not ftp
• the protocol should be added at the beginning of the URL
• the port should be added at the end of the URL after a colon.

Add an environment variable WGETRC and assign to it the name of the previous .ini file (Right click Computer, Properties, Advanced system parameters, Environment variables, Add).

If your proxy return error 407, AFAIK you must wait some time and retry later.

I wonder why several executables of wget are installed with CT ?
Now I have 3 of them, the 2 installed with CT and the one I downloaded from SourceForge before I discovered it was already installed...
Which one is used ?

As others, I suggest using Synapse and it's proxy properties, to remove needs for this external utility. It would be much simpler to setup.

Regards

Tintinux

Thanks Sir
wget is a must for many OSes
We use this program for stability and Host OS compatibility,
we must keep downloads and update CT procedures separate from CT programming core.

Synapse is the best solution, but many OSes have their "secrets",
can Synapse work OK on Solaris?
who can test Synapse on PCBSD?

All other version of wget is for other OSes
yes, we use HTTP protocol not ftp

www.pilotlogic.com/codetyphon/
CT stable version: www.pilotlogic.com/codetyphon/current/
CT Lab version: www.pilotlogic.com/codetyphon/development/
Toolchains :http://www.pilotlogic.com/codetyphon/toolchains/
Libraries: www.pilotlogic.com/codetyphon/libraries/

tintinux wrote: we must know that CT is using http protocol, not ftp

You only need to know exact address, protocol and port of your proxy server. Protocol that is used to get files from CT servers (or any other server) is irrelevant for setting proxy support for any software (including wget).

Since proxy is not always on 8080, it would be more appropriate to wrote this:

wget help is not bad at all, but windows port of wget have almost no documentation. Chapter from original documentation dedicated to proxy support can be found here in case anyone need it for some reason.

sternas wrote: wget is a must for many OSes
We use this program for stability and Host OS compatibility,

Have you ever consider to switch to cURL?

cURL supports download (and upload) using many protocols and is available on more OSes than wget. Also, as far as I know wget doesn't supports SOCKS proxy at all.

I used wget for years, but recently I started to replace wget with cURL in my scripts.

Thanks Sir
we must check this