Hans | Pixel Creation
My feedback
6 results found
-
87 votes
An error occurred while saving the comment Hans | Pixel Creation
supported this idea
·
-
290 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.
—
ETAn error occurred while saving the comment Hans | Pixel Creation
commented
This was one of the reasons we chose to never host any e-mail on our Plesk servers at all for any of our customers but only use services like Office 365 and Postmark. Such a shame.
An error occurred while saving the comment Hans | Pixel Creation
commented
"only raise prices" isn't fair. They've been doing a lot of updating and improving.
Problem is, this very basic and fundamental security feature hasn't had ANY priority for well over five years now.
As someone else stated: This is not a feature that should be considered given enough popular demand. It's a basic feature that should just be there.
An error occurred while saving the comment Hans | Pixel Creation
commented
I'm having to tell our customers we can't offer something that our competitors do. Please make this a priority.
Hans | Pixel Creation
supported this idea
·
-
561 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.
—
IGHans | Pixel Creation
supported this idea
·
-
6 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.
—
IGAn error occurred while saving the comment Hans | Pixel Creation
commented
When in Hosting Settings setting the Preferred Domain to anything but "None" and enabling "Permanent SEO-safe 301 redirect from HTTP to HTTPS" Plesk will redirect every request in one go.
For example, I configure my domain to redirect HTTP to HTTPS and to prefer the absence of "www". When I now request "http://www.example.com/" it will be redirected to "https://example.com/" in one single redirect. According to the Dutch Web application guidelines the server should first redirect to HTTPS and only then redirect to either include or exclude the www subdomain. (see attachment, taken from https://en.internet.nl/)
Hans | Pixel Creation
supported this idea
·
-
1 vote
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.
—
IGHans | Pixel Creation
shared this idea
·
-
20 votesHans | Pixel Creation
supported this idea
·
Some of our customers have raised their concerns over this. From the customer's perspective it might not be very harmful to have port 8443 accessible from their domain, but it is confusing when they can get an invalid certificate error on their domain. It's very tough to explain to them why it doesn't matter much.
This makes it important to us to be fixed. For now, we totally removed the ability to access from port 8443, which is NOT what we want, but for now the only way to work around these customer's concerns.