On 5/22/2015 3:25 AM, Mark Waddingham wrote:
Dave's patch to libURL should solve the issue for you.
Just to confirm: the patch does solve the problem. We just ran a test
and the data is coming through as expected. This is a big relief.
Thank you all so much. Now we just need to figure out wh
On 5/22/2015 3:25 AM, Mark Waddingham wrote:
Thus it seems to me that Dave is correct - this is actually a bug in
libURL - it is being too lax when parsing headers and interpreting a
header it should not be thus meaning it is not entering into 'chunked'
mode even though it is explicitly specified
On 2015-05-21 23:44, J. Landman Gay wrote:
To be honest, you've been more help than anyone else, for which I'm
really grateful. She originally contacted the Passenger forum and they
had little to offer outside of "your app should be handling the
chunking. Not our problem." And then they locked th
On 5/21/2015 4:11 PM, Dave Cragg wrote:
You could modify libUrl. :-) Perhaps not an option if you have many
users of the software. But it might be worth trying to confirm this
is the problem:
I'll keep your notes and if I get some energy I'll see. We've been
fighting with this for 2 weeks and
Dave Cragg writes:
> Under rfc-talk, that sounds a little like "shouldn’t contain" rather than
> "mustn’t contain". I can see blame going in both directions here.
LOL. Agreed.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode mailing list
use-li
> On 21 May 2015, at 20:07, J. Landman Gay wrote:
>>
>> I think that will pick up any Content-Transfer-Encoding header if it
>> exists before a Transfer-Encoding header, and therefore miss the
>> "chunked" value, and so not try to de-chunk the data. (I guess that
>> might be considered a bug in
On 5/21/2015 2:37 PM, Mark Wieder wrote:
J. Landman Gay writes:
So is this something you think I should report? Or is it just a
side-effect of working with different servers? There is a workaround;
specifying a Content-Length header appears to eliminate both the
"Content-Transfer-Encoding" and
J. Landman Gay writes:
> So is this something you think I should report? Or is it just a
> side-effect of working with different servers? There is a workaround;
> specifying a Content-Length header appears to eliminate both the
> "Content-Transfer-Encoding" and "Transfer-Encoding: chunked" hea
On 5/21/2015 3:42 AM, Dave Cragg wrote:
Is there really a "Content-Transfer-Encoding" line among the headers?
Yup, there is, and it happens to occur before the Transfer-Encoding header.
If so, that may be part of the problem. As far as I know,
"Content-Transfer-Encoding" is not a valid http h
> On 21 May 2015, at 04:17, J. Landman Gay wrote:
>
> Thanks for this, Dave. I don't see any chunk markers in the file with the
> version of libURL I'm using, I see rows of plain text. But even though the
> Content-Encoding header indicates it's a gzip file, it isn't coming in as
> one. The d
On 5/20/2015 6:47 PM, Dave Cragg wrote:
It should just return the content without the chunk marker thingies.
I’m using an older version. But if you run this script in a card with two fields, you
should see it is using "chunked" encoding. The returned data in field 2 has no
chunk markers. Is t
> On 20 May 2015, at 22:38, J. Landman Gay wrote:
>
> On 5/20/2015 2:06 PM, J. Landman Gay wrote:
>> we're trying to figure out how to avoid Passenger's addition of the
>> "chunking" header. Does anyone know of a related header we can include
>> that will make Passenger think we want a content-l
On 5/20/2015 2:06 PM, J. Landman Gay wrote:
we're trying to figure out how to avoid Passenger's addition of the
"chunking" header. Does anyone know of a related header we can include
that will make Passenger think we want a content-length instead?
Figured this out. If the server specifically se
Oops, I should have said we're running the app in 6.6.5. Doesn't change
anything though.
On 5/20/2015 2:06 PM, J. Landman Gay wrote:
Earlier this month, this happened:
On May 5, 2015 6:17:48 PM CDT, Trevor DeVore <[hidden email]> wrote:
>On Tuesday, May 5, 2015, Dave Cragg <[hidden email]>
Earlier this month, this happened:
On May 5, 2015 6:17:48 PM CDT, Trevor DeVore <[hidden email]> wrote:
>On Tuesday, May 5, 2015, Dave Cragg <[hidden email]>
>wrote:
>>
>>
>> From memory, I think the size of each chunk is sent with each chunk
>itself
>> in the message portion of the reply, not i
15 matches
Mail list logo
