Anonymous
My feedback
8 results found
-
532 votesAnonymous supported this idea ·
-
19 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment Anonymous supported this idea · -
208 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGAnonymous supported this idea · -
238 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
Anonymous supported this idea · -
412 votes
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
The original request contains a manual solution, so, we consider to automate it. Please, add a comment if your case will not be solved with that solution.
Thanks in advance!
— rk
Anonymous supported this idea · -
442 votesAnonymous supported this idea ·
-
1,271 votesAnonymous supported this idea ·
-
629 votes
Repeatedly we're seeing questions on when http/3 will be implemented. http/3 is available in the experimental branch of Nginx, called "main line". This is not a branch that is "stable". Plesk only offers stable software versions for the utmost reliability you can get as reliability is much more important than speed. A fast website is of no use if its webserver crashes or the protocol doesn't work as expected in all cases. Plesk does not offer experimental features. The stable version of Nginx that supports http/3 is expected to become available in April 2024. This is when it makes sense for Plesk to also offer http/3.
From articles that foster the hype about http/3, it sounds as if it can increase a website's speed incredibly much. On average, on real website tests by several reknown sources, the acceleration has been seen at around 0.2 to 0.3 s/page, typically around 12…
An error occurred while saving the comment Anonymous commentedHow is this not a thing in Obsidian?
Anonymous supported this idea ·
There should be at least a option to separately allow / disallow specific sections.
Right now, when you allow performance settings, the customer also get's access to the PHP-FPM settings which is a problem for us.