Xojo Conferences
MBSOct2019CologneDE

Weird characters in result when using httpSocket (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: Network Serial Checking
Next thread: [IGNORE] sig test


Re: Serializable ... kind of   -   Jan Erik Moström <
  Weird characters in result when using httpSocket   -   Jann Linder
   Re: Weird characters in result when using httpSocket   -   Frank Bitterlich
   [MWRB] CD Session Burner   -   James Sentman

Weird characters in result when using httpSocket
Date: 06.05.02 21:33 (Mon, 06 May 2002 13:33:47 -0700)
From: Jann Linder
When I use httpSocket, the first few characters are garbage and the last
couple are garbage. The content is always just fine...

It is just surrounded by things like:

24b

<BEGIN DATA


END DATA>

0

The 24b and the newline at the start, as well as the newline and the zero at
the end should not be there. Any idea why this is happening?

I am in the DLFinished event of httpSocket when I get this. The only Kbase
article I found said that therer could be errors in DataAvailable when
getting data from a second thread....whatever the heck that means.

TIA
Jann



---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>

Re: Weird characters in result when using httpSocket
Date: 14.05.02 17:06 (Tue, 14 May 2002 18:06:38 +0200)
From: Frank Bitterlich
I don't know httpSocket, but what does the Content-Type header of the
URL you're trying to get say?

Cheers,
Frank+++

Jann Linder wrote:
>
> When I use httpSocket, the first few characters are garbage and the last
> couple are garbage. The content is always just fine...
>
> It is just surrounded by things like:
>
> 24b
>
> <BEGIN DATA
>
> END DATA>
>
> 0
>
> The 24b and the newline at the start, as well as the newline and the zero at
> the end should not be there. Any idea why this is happening?
>
> I am in the DLFinished event of httpSocket when I get this. The only Kbase
> article I found said that therer could be errors in DataAvailable when
> getting data from a second thread....whatever the heck that means.