Hi,
I have a client service that connects and gathers data and then throws
this data out in a stream on port 60500. This client is 3rd party and I
cannot alter it. However, it is known to be working product.
What I need to be able to do is connect to that stream stream of data on
port 60500, a
Hello,
I am trying to fix digest authentication coded by Peter. We have a big
problem with Internet Explorer. In the setup below, you will see a web page
requested without first sending the "Authorization:" header. Then the server
responds with 401 and tells the client it prefers "Digest" auth
Dont you connect to port 60500 instead of listening on it? Something is
already listening on that port.
Dan.
- Original Message -
From: "David Lewis" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 24, 2006 10:16 AM
Subject: [twsocket] Port Access
> Hi,
>
> I ha
Hello David,
The port is in use because the server listens on that port already,
otherwise the client could not send it to that server. You can make the
server listen on another port and then your application should act like
a proxy intercepting all data. See SocketSpy or gpHttpProxy for example.
Scrive Fastream Technologies <[EMAIL PROTECTED]>:
> Hello,
>
> I am trying to fix digest authentication coded by Peter. We have a big
> problem with Internet Explorer. In the setup below, you will see a web page
> requested without first sending the "Authorization:" header. Then the server
I t
Maurizio Lotauro wrote:
> Scrive Fastream Technologies <[EMAIL PROTECTED]>:
>
>> Hello,
>>
>> I am trying to fix digest authentication coded by Peter. We have a big
>> problem with Internet Explorer. In the setup below, you will see a web page
>> requested without first sending the "Authorizatio
Hello,
Thank you both for your replies. I found the problem myself: IE6 has a bug
that makes it expect a comma before Realm="...". Should be like:
HTTP/1.1 401 Authorization Required..WWW-Authenticate: Digest Basic, (HERE
HERE!)
realm=localhost/%3EFastream.com/, uri="localhost/%3EFastream.com/"
Fastream Technologies wrote:
> Hello,
>
> Thank you both for your replies. I found the problem myself: IE6 has a bug
> that makes it expect a comma before Realm="...".
That's really weird. Does adding the comma break it on Firefox or
Opera? The RFC does not specify that a comma is required, o
Firefox and Opera tolerates the comma well. You can try here:
http://www.fastream.net/beta/NetFileServer.exe (8.0.8B2). Just add a user
from HTTP->Users and then assign the user to a path (C:\NFRoot is the
default) and point your browser to localhost. I believe Mozilla team knew
about the IE b
Scrive DZ-Jay <[EMAIL PROTECTED]>:
> Maurizio Lotauro wrote:
> > Scrive Fastream Technologies <[EMAIL PROTECTED]>:
[...]
> >> 24.01.2006 13:31:57 From Remote
> >>
> >> HTTP/1.1 401 Authorization Required..WWW-Authenticate: Digest Basic
> >> realm=localhost/%3EFastream.com/, uri="localhost/%3EFa
Scrive DZ-Jay <[EMAIL PROTECTED]>:
> Fastream Technologies wrote:
> > Hello,
> >
> > Thank you both for your replies. I found the problem myself: IE6 has a bug
>
> > that makes it expect a comma before Realm="...".
>
> That's really weird. Does adding the comma break it on Firefox or
> Opera?
Scrive Fastream Technologies <[EMAIL PROTECTED]>:
> Firefox and Opera tolerates the comma well. You can try here:
> http://www.fastream.net/beta/NetFileServer.exe (8.0.8B2). Just add a user
> from HTTP->Users and then assign the user to a path (C:\NFRoot is the
> default) and point your browse
Maurizio Lotauro wrote:
> Scrive Fastream Technologies <[EMAIL PROTECTED]>:
>
>> Firefox and Opera tolerates the comma well. You can try here:
>> http://www.fastream.net/beta/NetFileServer.exe (8.0.8B2). Just add a user
>> from HTTP->Users and then assign the user to a path (C:\NFRoot is the
>
Hello,
- Original Message -
From: "Maurizio Lotauro" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 24, 2006 6:54 PM
Subject: Re: [twsocket] Need help with RFC2617 and IE bug
> Scrive DZ-Jay <[EMAIL PROTECTED]>:
>
>> Maurizio Lotauro wrote:
>> > Scrive Fastream Te
- Original Message -
From: "Maurizio Lotauro" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 24, 2006 6:59 PM
Subject: Re: [twsocket] Need help with RFC2617 and IE bug
> Scrive DZ-Jay <[EMAIL PROTECTED]>:
>
>> Fastream Technologies wrote:
>> > Hello,
>> >
>> > Than
Maurizio Lotauro wrote:
> Scrive DZ-Jay <[EMAIL PROTECTED]>:
>
>> Fastream Technologies wrote:
>>> Hello,
>>>
>>> Thank you both for your replies. I found the problem myself: IE6 has a bug
>>> that makes it expect a comma before Realm="...".
>> That's really weird. Does adding the comma break it
Maurizio Lotauro wrote:
> Scrive DZ-Jay <[EMAIL PROTECTED]>:
>
>> Maurizio Lotauro wrote:
>>> Scrive Fastream Technologies <[EMAIL PROTECTED]>:
>
> [...]
>
24.01.2006 13:31:57 From Remote
HTTP/1.1 401 Authorization Required..WWW-Authenticate: Digest Basic
realm=localhost/%3E
- Original Message -
From: "DZ-Jay" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 24, 2006 7:25 PM
Subject: Re: [twsocket] Need help with RFC2617 and IE bug
> Maurizio Lotauro wrote:
>> Scrive DZ-Jay <[EMAIL PROTECTED]>:
>>
>>> Fastream Technologies wrote:
He
(Sorry for my last message, I click "Send" before I wrote anything on it!)
Maurizio Lotauro wrote:
> Are you sure? I quickly reread the rfc and it say that more that one
> challange
> could be specified in the header, but a challenge is defined as
>
> challenge = auth-scheme 1*SP 1#auth-para
Fastream Technologies wrote:
> - Original Message -
> I have read the RFC but as I wrote half an hour ago, it is the MS guys that
> did not read it well. Or perhaps they developed when the RFC was a draft
> which has later been changed.
My comment was directed at Maurizio.
>> Conclusi
- Original Message -
From: "DZ-Jay" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 24, 2006 7:48 PM
Subject: Re: [twsocket] Need help with RFC2617 and IE bug
> Fastream Technologies wrote:
>> - Original Message -
>
>> I have read the RFC but as I wrote ha
Hello,
I have a client/server application. Clients connect to Server. If client reboot
the machine by pressing the case reboot button or plug out the UTP cable,
Server will not be immediatelly informed for that disconnection.
I know this is Windows TCP/IP limitation, so I want to ask if there is
- Original Message -
From: "George" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, January 24, 2006 7:42 PM
Subject: [twsocket] Absnormal disconnection
> Hello,
>
> I have a client/server application. Clients connect to Server. If client
> reboot the machine by pressing the case reboot button
Scrive DZ-Jay <[EMAIL PROTECTED]>:
> Maurizio Lotauro wrote:
> > Scrive Fastream Technologies <[EMAIL PROTECTED]>:
> >
> >> Firefox and Opera tolerates the comma well. You can try here:
> >> http://www.fastream.net/beta/NetFileServer.exe (8.0.8B2). Just add a user
>
> >> from HTTP->Users and th
Scrive Fastream Technologies <[EMAIL PROTECTED]>:
> Hello,
>
> - Original Message -
> From: "Maurizio Lotauro" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Tuesday, January 24, 2006 6:54 PM
> Subject: Re: [twsocket] Need help with RFC2617 and IE bug
>
>
> > Scrive DZ-Jay <[
Scrive DZ-Jay <[EMAIL PROTECTED]>:
> Maurizio Lotauro wrote:
> > Scrive DZ-Jay <[EMAIL PROTECTED]>:
> >
> >> Fastream Technologies wrote:
> >>> Hello,
> >>>
> >>> Thank you both for your replies. I found the problem myself: IE6 has a
> bug
> >>> that makes it expect a comma before Realm="...".
>
Scrive Fastream Technologies <[EMAIL PROTECTED]>:
[...]
> I fully agree. However we need to support both standards otherwise we would
> be sacrificing 80% of the surfers.
So at this point why don't write each challenge in different header? In that
case you should not write it in a "wrong" way
Scrive DZ-Jay <[EMAIL PROTECTED]>:
> (Sorry for my last message, I click "Send" before I wrote anything on it!)
No problem :-)
> Maurizio Lotauro wrote:
>
> > Are you sure? I quickly reread the rfc and it say that more that one
> challange
> > could be specified in the header, but a challenge
28 matches
Mail list logo