Thanks Dan. I did finally figure this out. Unfortunately I'm a complete newb to this, I've been supporting COTS apps for 20 years. This open source dev stuff is new to me.

________________________________
From: curl-library on behalf of curl-library-request_at_cool.haxx.se
Sent: Tuesday, December 30, 2014 5:42:31 PM
To: curl-library_at_cool.haxx.se
Subject: curl-library Digest, Vol 112, Issue 45

Send curl-library mailing list submissions to
        curl-library_at_cool.haxx.se

To subscribe or unsubscribe via the World Wide Web, visit
        http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library
or, via email, send a message with subject or body 'help' to
        curl-library-request_at_cool.haxx.se

You can reach the person managing the list at
        curl-library-owner_at_cool.haxx.se

When replying, please edit your Subject line so it is more specific
than "Re: Contents of curl-library digest..."

Today's Topics:

   1. RE: Patches to winbuild for support of c-ares and OpenSSL
      debug (Steve Holme)
   2. Re: Patches to winbuild for support of c-ares and OpenSSL
      debug (Sam)
   3. RE: Patches to winbuild for support of c-ares and OpenSSL
      debug (Steve Holme)
   4. Need Help Please (Jones, Rick)
   5. WPAD proxy (was Re: Need Help Please) (Dan Fandrich)
   6. Re: WPAD proxy (was Re: Need Help Please) (Ralph Mitchell)

----------------------------------------------------------------------

Message: 1
Date: Tue, 30 Dec 2014 12:03:17 +0000
From: Steve Holme <steve_holme_at_hotmail.com>
To: "'libcurl development'" <curl-library_at_cool.haxx.se>
Subject: RE: Patches to winbuild for support of c-ares and OpenSSL
        debug
Message-ID: <DUB408-EAS113F9E0BA4FBE69861BA3E9825E0_at_phx.gbl>
Content-Type: text/plain; charset="UTF-8"

On Tue, 30 Dec 2014, Sam wrote:

> I'm submitting the attached patches for consideration, which I
> have used for my own build. I am building on Windows 8, using
> nmake from the developer console supplied with Visual Studio
> 2013 Express.

Thank you for your submission and work on this.

> One patch adds support for linking against the debug versions of
> OpenSSL libraries when building a debug version of libcurl.

What version of OpenSSL are you using and what commands did you use to build OpenSSL?

> The other adds support for linking against c-ares, and enabling its use
> through the USE_ARES symbol definition.

This patch looks pretty good to me.

Kind Regards

Steve

------------------------------

Message: 2
Date: Tue, 30 Dec 2014 11:00:48 -0800
From: Sam <windexlight_at_gmail.com>
To: libcurl development <curl-library_at_cool.haxx.se>
Subject: Re: Patches to winbuild for support of c-ares and OpenSSL
        debug
Message-ID:
        <CAFM7F++33z2-2YajuWNJcPJLJ9cA0jHak2kYr2f=QRegVPRwNg_at_mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

> What version of OpenSSL are you using and what commands did you use to build OpenSSL?

I am using OpenSSL 1.01j. I actually did not build it, but rather
took the lazy shortcut and downloaded binaries from
http://www.npcglib.org/~stathis/blog/precompiled-openssl/

I've just noticed, reading through the notes there, that the fellow
doing the building states: "The main difference from the official
release is that I patch the sources to allow compiling libraries with
filenames that reflect the compile configuration, which makes it
easier to use later." I would read that to mean that his library
names might be non-standard, so perhaps this patch is not suitable for
general use. Though there still exists the issue on Windows that you
must build a project with consistent linkage against the same versions
of the CRT, or you will get errors/warnings. That is what led me to
set up linking against the debug versions of OpenSSL in the first
place.

Thanks,
Sam

------------------------------

Message: 3
Date: Tue, 30 Dec 2014 20:14:25 +0000
From: Steve Holme <steve_holme_at_hotmail.com>
To: "'libcurl development'" <curl-library_at_cool.haxx.se>
Subject: RE: Patches to winbuild for support of c-ares and OpenSSL
        debug
Message-ID: <DUB408-EAS4257E7AC005A9163D4CD17B825E0_at_phx.gbl>
Content-Type: text/plain; charset="UTF-8"

On Tue, 30 Dec 2014, Sam wrote:

> > What version of OpenSSL are you using and what commands
> > did you use to build OpenSSL?
>
> I am using OpenSSL 1.01j. I actually did not build it, but rather took
> the lazy shortcut and downloaded binaries from
> http://www.npcglib.org/~stathis/blog/precompiled-openssl/
>
> I've just noticed, reading through the notes there, that the fellow
> doing the building states: "The main difference from the official release
> is that I patch the sources to allow compiling libraries with filenames that
> reflect the compile configuration, which makes it easier to use later."
>
> I would read that to mean that his library names might be non-standard,
> so perhaps this patch is not suitable for general use.

Ah Yes...

Unfortunately the OpenSSL build system isn't great for side-by-side builds under Windows either debug and release or different versions of Visual Studio etc...

> Though there still exists the issue on Windows that you must build a project
> with consistent linkage against the same versions of the CRT, or you will get
> errors/warnings. That is what led me to set up linking against the debug
> versions of OpenSSL in the first place.

Kind of...

If you are building a debug version of libcurl, you can link against the release version of OpenSSL. The only thing you won't be able to do is debug the OpenSSL functions.

I don't think you can mix /MD and /MT builds - but I only use the "out of the box" version of OpenSSL and assume it uses /MD (dynamic CRT) even for the static builds as I don't run into any issues with our Visual Studio project file based builds where we only support the dynamic CRT at present (/MD and /MDd). Note: In these project files we support the following configurations which may be of interest to you rather than using the makefiles:

* A static version of libcurl that links against the static version of OpenSSL
* A static version of libcurl that links against the DLL version of OpenSSL
* A DLL version of libcurl that links against the DLL version of OpenSSL

If memory serves me correctly, you couldn't mix the threading models, but I've not used the single threaded libraries for years - are they still available?

Kind Regards

Steve

------------------------------

Message: 4
Date: Tue, 30 Dec 2014 14:58:52 +0000
From: "Jones, Rick" <Rick.Jones_at_finra.org>
To: "curl-library_at_cool.haxx.se" <curl-library_at_cool.haxx.se>
Subject: Need Help Please
Message-ID:
        <A465A5FCCE409141A565BD0BDD7DF8467355F297_at_NY4WNEXMBP002.corp.root.nasd.com>

Content-Type: text/plain; charset="utf-8"

I have packaged cURL for my enterprise developers to use when needed but am having some issues.

The installation part is easy, but I need to modify my package due to a configuration issue. Please let me explain.

We are in a very locked down environment; users and devs do not have access rights to their machines; so everything must be packaged for them and installed via SCCM.

The problem is our proxy, we are using WPAD to get to an external proxy which lets people out. What settings do I need to modify in order to use cURL? I have tried setting http_proxy and https_proxy but I'm still unable to connect.

This would be for 64-bit Windows 7 Enterprise machines.

Any help would be greatly appreciated. If more information is needed, please let me know.

Thanks,

Rick Jones
Enterprise Desktop Engineering
9509 Key West Ave.
Rockville, MD 20850
(W) 240-386-4992
(C) 240-305-3981
Did You Know<http://finranet.finra.org/Technology/euts/Pages/DYK.aspx>

Confidentiality Notice:: This email, including attachments, may include non-public, proprietary, confidential or legally privileged information. If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cool.haxx.se/pipermail/curl-library/attachments/20141230/902c4fd8/attachment-0001.html>

------------------------------

Message: 5
Date: Tue, 30 Dec 2014 23:30:27 +0100
From: Dan Fandrich <dan_at_coneharvesters.com>
To: curl-library_at_cool.haxx.se
Subject: WPAD proxy (was Re: Need Help Please)
Message-ID: <20141230223027.GA9154_at_coneharvesters.com>
Content-Type: text/plain; charset=iso-8859-7

On Tue, Dec 30, 2014 at 02:58:52PM +0000, Jones, Rick wrote:
> I have packaged cURL for my enterprise developers to use when needed but am
> having some issues.
>
> The installation part is easy, but I need to modify my package due to a
> configuration issue. Please let me explain.
>
> We are in a very locked down environment; users and devs do not have access
> rights to their machines; so everything must be packaged for them and installed
> via SCCM.
>
> The problem is our proxy, we are using WPAD to get to an external proxy which
> lets people out. What settings do I need to modify in order to use cURL? I
> have tried setting http_proxy and https_proxy but I’m still unable to connect.

WPAD generally provides a small Javascript program that's executed by the
browser to determine which sites to send to a proxy and which proxy to use.
curl doesn't contain a Javascript interpreter, so it can't use such a proxy
configuration directly. It's (theoretically) possible to integrate a standalone
Javascript interpreter with libcurl to handle this kind of proxy configuration,
but it wouldn't be trivial. See the mailing list archives for previous
questions about this.

Alternately, for certain simple cases you could manually interpret the proxy
configuration, extract the correct proxy server for the site(s) you're
interested in, and provide that proxy server in http_proxy.

>>> Dan

------------------------------

Message: 6
Date: Tue, 30 Dec 2014 17:42:23 -0500
From: Ralph Mitchell <ralphmitchell_at_gmail.com>
To: libcurl development <curl-library_at_cool.haxx.se>
Subject: Re: WPAD proxy (was Re: Need Help Please)
Message-ID:
        <CAAEjoCWRwT8X+HAFw6rn3R4fH6bi2wZCZmn6VjQ0Zr+OXHxrkQ_at_mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Tue, Dec 30, 2014 at 5:30 PM, Dan Fandrich <dan_at_coneharvesters.com>
wrote:

> On Tue, Dec 30, 2014 at 02:58:52PM +0000, Jones, Rick wrote:
> > I have packaged cURL for my enterprise developers to use when needed but
> am
> > having some issues.
> >
> > The installation part is easy, but I need to modify my package due to a
> > configuration issue. Please let me explain.
> >
> > We are in a very locked down environment; users and devs do not have
> access
> > rights to their machines; so everything must be packaged for them and
> installed
> > via SCCM.
> >
> > The problem is our proxy, we are using WPAD to get to an external proxy
> which
> > lets people out. What settings do I need to modify in order to use
> cURL? I
> > have tried setting http_proxy and https_proxy but I’m still unable to
> connect.
>
> WPAD generally provides a small Javascript program that's executed by the
> browser to determine which sites to send to a proxy and which proxy to use.
> curl doesn't contain a Javascript interpreter, so it can't use such a proxy
> configuration directly. It's (theoretically) possible to integrate a
> standalone
> Javascript interpreter with libcurl to handle this kind of proxy
> configuration,
> but it wouldn't be trivial. See the mailing list archives for previous
> questions about this.
>
> Alternately, for certain simple cases you could manually interpret the
> proxy
> configuration, extract the correct proxy server for the site(s) you're
> interested in, and provide that proxy server in http_proxy.
>

That little bit of Javascript is probably a proxy-auto-config (.pac) file.
I put in a few minutes way back when to see if we could automate processing
those. See this post for details on handling .pac in a script:

     http://curl.haxx.se/mail/archive-2002-06/0104.html

As long as you know where to get the .pac file, you may be able to exec a
script from your program to process it and return something usable. Dunno
how you'd do that in Windows, though.

Ralph Mitchell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cool.haxx.se/pipermail/curl-library/attachments/20141230/46915c17/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
curl-library mailing list
curl-library_at_cool.haxx.se
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library

------------------------------

End of curl-library Digest, Vol 112, Issue 45
*********************************************

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-12-31