Sorry for the confusion. I meant there should be a new event with a
reference String variable which would be set by the application programmer
to set the NTLM domain before the NTLM message 1 is sent. Or maybe there
could just be a new String property which would be null by default (for the
What our users need from our reverse proxy is to be able to connect to NTLM
domain #1 for a URL such as www.domain.com/app1 and NTLM domain #2 for a URL
such as www.domain.com/app2. It could be some other HTTP domain as well
(multi-homed). So we need a flexible solution such as the one I described.
On Thu, Dec 16, 2010 at 3:21 PM, Arno Garrels <arno.garr...@gmx.de> wrote:
> Fastream Technologies wrote:
> > Anybody else who need this feature want to be a sponsor for it? As I
> > said we offer $180 if it could be completed until January 1st.
> > Anybody else who need this feature want to be a sponsor for it? As I said
> > offer $180 if it could be completed until January 1st.
> Your offer was:
> > I thought I should have made our offer more concrete. We would like to
> > $180 to a coder who can make the ICS code advancement so that an event
> > a reference variable called NTLMDomain would return the NTLM domain to
> > authenticate against after the request is received for HTTPS server.
> > interested should contact me from ga...@fastream.com. We can pay with
> > Paypal.
> I wonder what you mean by "feature"? Just "returning" the target domain is
> easy task. At least you should be able to phrase the task correctly or pay
> somebody else to do it for you.
> Arno Garrels
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be