Yep, that does the trick!
<use_enriched_content_type>N</use_enriched_content_type>
<padding>2048</padding>
Type: Posts; User: abcdefg
Yep, that does the trick!
<use_enriched_content_type>N</use_enriched_content_type>
<padding>2048</padding>
Yep.
Locally yes. I'm trying to avoid server upgrades because our deployment scripts are ... less than fully understood.
I just checked again to make sure. Yes.
Hmm. After returning to the problem a week later, I can't reproduce my own results.
I'm getting the behaviour I stated for the 5.1.2 server, but not for the 6.0.3 any more. (I think perhaps I just...
Could you just confirm for me that you can NOT reproduce this behaviour
Server: Lightstreamer 6.0.3
Server setting: <use_enriched_content_type>N</use_enriched_content_type>
Client:...
I think I might have isolated the problem.
Our servers run Lightstreamer 5.1.1. In 5.1.2 you added the <use_enriched_content_type> property which changes the Content-Type of messages from...
No problem, I've attached.
In the server logs, it looks like the header checksums are ok in both directions, so I'm guessing that this is just a recording quirk.
It is interesting however apparently a 0x0000 checksum might just be a quirk of Wireshark when capturing the packets.
...
Thanks for the clarification, that makes sense now.
I've added those extra log settings and attached the updated server log.
And also I have a Wireshark .pcapng which shows what the...
Okay I am very confused now.
Here is the first bit of my lightstreamer_conf.xml file:
<?xml version="1.0"?>
<lightstreamer_conf>
Thanks for the help Giuseppe
I've made those changes and I have another log file for you but I can still see keepalive mentioned in there ...
Should be attached to this post.
Hi
1. Well I know that the server does support both iOS and Android because it's working for plenty of our live users on those platforms. But I don't know how to verify this formally. But I don't...
Hi there.
I am trying to connect to a Lightstreamer server but the connection stalls at the bind_session.txt step.
I can replicate this behaviour in Postman, calling create_session.txt...