Jacob Kelly
My feedback
21 results found
-
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…
Jacob Kelly supported this idea · -
220 votesJacob Kelly supported this idea ·
-
467 votesJacob Kelly supported this idea ·
-
107 votesJacob Kelly supported this idea ·
-
24 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.— rk
Jacob Kelly supported this idea · -
17 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.
—
IGJacob Kelly supported this idea · -
96 votesJacob Kelly supported this idea ·
-
56 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.
—
AAJacob Kelly supported this idea · -
44 votesJacob Kelly supported this idea ·
-
75 votesJacob Kelly supported this idea ·
-
532 votesJacob Kelly supported this idea ·
-
27 votesJacob Kelly supported this idea ·
-
40 votes
This is a valid request. 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.
-- PD
Jacob Kelly supported this idea · -
25 votes
In the initital feature request it was not clear that the focus was on a regex driven, variable redirect that depends on source URLs and should be able to provide a mapping between source and target. It is also requested that these redirects shall be done on the front-end web server level, not as an Apache .htaccess solution.
We have re-opened the request as per user comment it was clarified thoroughly. 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.
-- PD
Jacob Kelly supported this idea · -
697 votesJacob Kelly supported this idea ·
-
100 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.-DL
Jacob Kelly supported this idea · -
201 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.
—
ETJacob Kelly supported this idea · -
68 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.—
IGJacob Kelly supported this idea · -
202 votesJacob Kelly supported this idea ·
-
17 votesJacob Kelly supported this idea ·