Hi Phil,
I absolutely agree with Matthias - the first thing to try (if you didn't
already) is a custom-install of the older LC server version that you
were using pre-upgrade.
However, it would also help to clarify the bug report somewhat. My
reading of it is (almost) the opposite of Mathias's - i.e. I think
you're posting a large file to the server.
If so, what happens to the large file - is it simply stored by the LC
server, or does it need to be processed ?
If that is the case, can you write a tiny .lc server script that just
receives and stores it ?
Can you add logging statements to the server script to verify if *it*
sees the post arrive ?
If the tiny script works - could you (as a test and/or a temp
workaround) store that file on the server (e.g. in /tmp) and return the
tmp filename, and then have a second request that processes it ?
Alex.
On 07/05/2020 09:34, matthias rebbe via use-livecode wrote:
Phil,
you are not mentioning how you do prepare the data which is posted to the
server.
Which engine is processing your post? PHP or LC Server?
In your bug report you are writing "to a large file". How big is "large"?
You are posting data to the server to get back the large file, right?
Is the file plain text or binary data?
If you are using LC Server scripts on your server to handle the posts...
Which version of LC Server was installed in your old hosting package?
- If it was a lower version than the currently installed one , then i would do
a custom install of that LC Server version that was installed on your old
hosting package and try with that version.
That could be done in some minutes.
Does the large file already exist on the server or is it created on the fly
when the data is posted to the server?
- If the file already exists on the server i would create a little .php or .lc
test script which just outputs/returns the file back when executed.
- If the file is created on the fly, then i would first create a large sample
file on the server and would then try with some test scripts.
This would show if the server has problems with large files in general, but i
doubt it has.
Is the file returned with http headers or just returned plain without any
headers?
Matthias
-
Matthias Rebbe
Life Is Too Short For Boring Code
Am 07.05.2020 um 09:17 schrieb Phil Davis via use-livecode
<use-livecode@lists.runrev.com>:
Has anyone had part or all of an on-rev server-based system stop working since
the server upgrades a month or so ago?
My client has an on-rev.com-based training system. Training delivery is via web
browser, and that part continues to work. But there are several desktop apps
that provide training development, management and real-time monitoring. All of
those apps became non-functional as soon as the upgrades were done, and remain
so. I haven't been able to figure out how to restore functionality.
Robin in on-rev support has been very helpful, but we still don't have a
solution. This is the bug report:
https://quality.livecode.com/show_bug.cgi?id=22704
I wouldn't wish this on anyone, but in a way I'm hoping it isn't just us.
Thanks -
Phil Davis
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
