POST /cornerstone-endpoint HTTP/2.0 crash

Support
#1

Hi,
I found a way to crash the server…The scenario:

  • Edit a page in cornerstone
  • Edit a text passage
  • Type quickly a new text

The server crashes.
In the log I find multiple lines like:
2019-03-05 16:24:21 Access 178.115.128.21 200 POST /cornerstone-endpoint HTTP/2.0 path/x/ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 3.41 K SSL/TLS-Zugriff für nginx
2019-03-05 16:24:22 Access 178.115.128.21 200 POST /cornerstone-endpoint HTTP/2.0 path/x/ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 3.43 K SSL/TLS-Zugriff für nginx
2019-03-05 16:24:22 Access 178.115.128.21 200 POST /cornerstone-endpoint HTTP/2.0 path/x/ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 3.39 K SSL/TLS-Zugriff für nginx
2019-03-05 16:24:23 Access 178.115.128.21 200 POST /cornerstone-endpoint HTTP/2.0 path/x/ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 3.40 K SSL/TLS-Zugriff für nginx

until
2019-03-05 16:24:36 Error 178.115.128.21 504 POST /cornerstone-endpoint HTTP/2.0 path/x/ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 578 SSL/TLS-Zugriff für nginx
2019-03-05 16:24:36 Error 178.115.128.21 504 POST /cornerstone-endpoint HTTP/2.0 path/x/ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 578 SSL/TLS-Zugriff für nginx
2019-03-05 16:24:36 Error 178.115.128.21 11968#0: *111325 upstream timed out (110: Connection timed out) while reading response header from upstream

My question: Is there a way of preventing this without having to edit offline and than copy/paste?

Thanks,
Matt

#2

Hi Matt,

It looks like your issue is related to these threads.


There are two ways to resolve this, increase your post limit in your server or type your content first in notepad or word then copy and paste your content.

Thanks

#3

Hi Paul,
thanks for the reply. I can increase the post limit. Is there a limit you would recommend so that typing text will always work?
I wonder though, if there is no way from a development perspective to cache cornerstone (in the browser) or on the server?
To be honest, we went through two server moves as no one could figure out that cornerstone was causing it…
All the best,
Matt

#4

Hi Matt,

Could you give the latest version a try and let us know if it works better? Rather than sending on every keystroke we added some throttling so it only fires a few times per second max. There is some caching. For example, if you backspace it won’t fire another request since it remembers the response from a previous request that was identical.

#5

Hi Alexander,
thanks. Right now we are on Version 3.4.6 of X, as we are on automatic update.
I guess you speak about 6.5?
Anyway, would you mind letting me know what you recommend for a post limit?
Tnx,
Matthias

#6

Hi Matthias,

Yes, Alex is referring to X 6.5.0, Cornerstone 3.5.0

Please check our changelog for full details regarding this new release

https://theme.co/changelog/

With regards to post limit, you can try increase it to 128M

post_max_size 128M

You might not need this as the new version has a throttling feature.

Thanks

#7

Hi Paul,
thank you for the message. As we run multiple domains, I had forgotten that I already had changed the post limit… Sorry for that. The limit was even 512M - still we have the crashes when typing too fast.
I guess, I will have to wait for the new version on autoupdate, as these are high traffic sites and I do not want to risk to test a new version on the beta channel.
Thank you,
Matthias

#8

Hello Matthias,

You might want to test drive the X 6.5.0 and Cornerstone 3.5.0 which is already available via automatic updates in a staging server if you have one to make sure that there aren’t any issues and without disrupting your live site. Once everything is perfect, you can easily and flawlessly proceed the update in the live site.

Please let us know how it goes.

#9

Thank you RueNel,
I upgraded already and will test again.
All the best,
Matt

#10

Sounds good Matt! Let us know how it goes.

#11

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.