Skip to content

Anonymous

My feedback

3 results found

  1. 26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Customers are asking for support for this format, please include it in the PHP versions where this is possible. It would make our lives and our customers a lot easier.

    Having to maintain an (unsupported) imagick extension is a burden. WEBP popularity is declining in favour of AVIF, which is also not supported with ImageMagick 6.9.

    We really would like to see Plesk's PHP versions support modern image formats such as AVIF, JPEG-XL, HEIF and of course HEIC. I know GD has support for AVIF, but this still does not enable us to support Mac / iOS users which would like to upload their HEIC photos. That would be the end goal. Thank you for considering this.

    Anonymous supported this idea  · 
  2. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Implementation of this "feature" should not depend on popularity. It is the only right *and* secure way to redirect from non-www to www domain. If this is not done, then the HSTS header is never sent for the non-www version of the domain, allowing MITM attacks / stripping HTTPS.

    IMHO Plesk should use the secure way by default: redirect from HTTP to HTTPS first (allowing the HSTS header to be sent) and *then redirect from non-www to www.

    If there really are people who wish to not do this, avoid one redirect and immediately redirect to https://www.domain.tld, then allow them to override the secure default. IMHO this is over-optimization, as these days (with HTTP/2) there is not nearly as much overhead as there was before.

    Please fix this if this is not done already. :-)

    Anonymous supported this idea  · 
  3. 24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 

Feedback and Knowledge Base