• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Forwarded to devs Error notification missing for forwarding domain back to itself

Kaspar

API expert
Plesk Guru
Username:

TITLE

Error notification missing for forwarding domain back to itself

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.64
OS: any

PROBLEM DESCRIPTION

When changing the Hosting Type for a domain to Forwarding you can't set an URL using the domain your forwarding from (because that would create an infinite loop). An error message is shown to the user when they trying to do this.

However, when a users changes an already existing forwarding URL to the same domain, no error message is shown. This might confuse users, as the new URL isn't saved (as it should).

STEPS TO REPRODUCE

1) Create subscription
2) Change hosting type of subscription to Forwarding, set URL to the same domain as the subscription.
- Notice how an error message shows "Redirect address can not be set to domain name."

3) Change hosting type to Forwarding, set URL to an external domain (for example plesk.com), and click save.
4) Open hosting settings again and change forwarding URL again to the same domain as the subscription and click save.
- Notice how there is no error message shown this time.

ACTUAL RESULT

No error message shown.

EXPECTED RESULT

Error message shown to indicate that forwarding URL can not be set to the domain name.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for the report, Kaspar. I was able to reproduce the behavior on a test environment and forwarded it to our engineers for further review.
 
@Kaspar, the behavior was identified as a bug with ID PPPM-14656. Thank you once again for bringing it to our attention. We will introduce a fix in one of the feature releases. Unfortunately, I cannot provide any ETA at the time being.
 
Back
Top