-
Suggestion
-
Resolution: Won't Do
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
We noticed today that a link, where the https:// was mistyped and was missing the final slash, got redirected as if it were a directory on the local web server, instead of just being a broken link. Would it be better to leave it broken, or to repair the link, instead of prefixing the local server to it?
Steps to reproduce:
1. Edit this page: https://wiki.cac.washington.edu/pages/viewpage.action?pageId=72219641
2. Insert a mistyped link: http:/washington.edu/calendar/trumba
3. Click Save
4. Go visit your link and see where it goes.
Expected:
1. Link would be "fixed" and extra / would be added after the http:/ so the link would go to its intended destination
or
2. Link would go to broken link that I typed in
or
3. I would have been notified after step 2 (or possibly after step 3) that I entered an invalid link
Actual:
https://wiki.cac.washington.edu/ is affixed to the beginning of my link making it:
https://wiki.cac.washington.edu/https:/washington.edu/calendar/trumba
I can understand why the software thought that the "https:/" could have been a directory, but this has been confusing for some of our users.
- relates to
-
CONFCLOUD-41519 https:/ is not treated as link prefix
- Closed
[CONFSERVER-41519] https:/ is not treated as link prefix
Workflow | Original: JAC Suggestion Workflow 4 [ 3577796 ] | New: JAC Suggestion Workflow 3 [ 4337237 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3171304 ] | New: JAC Suggestion Workflow 4 [ 3577796 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3031764 ] | New: JAC Suggestion Workflow 2 [ 3171304 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2530465 ] | New: JAC Suggestion Workflow [ 3031764 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2276871 ] | New: Confluence Workflow - Public Facing v4 [ 2530465 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Needs Verification [ 10004 ] | New: Resolved [ 5 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2173788 ] | New: Confluence Workflow - Public Facing v3 [ 2276871 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1947857 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2173788 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1753980 ] | New: Confluence Workflow - Public Facing v3 [ 1947857 ] |
Description |
Original:
We noticed today that a link, where the https:// was mistyped and was missing the final slash, got redirected as if it were a directory on the local web server, instead of just being a broken link. Would it be better to leave it broken, or to repair the link, instead of prefixing the local server to it?
Steps to reproduce: 1. Edit this page: https://wiki.cac.washington.edu/pages/viewpage.action?pageId=72219641 2. Insert a mistyped link: http:/washington.edu/calendar/trumba 3. Click Save 4. Go visit your link and see where it goes. Expected: 1. Link would be "fixed" and extra / would be added after the http:/ so the link would go to its intended destination or 2. Link would go to broken link that I typed in or 3. I would have been notified after step 2 (or possibly after step 3) that I entered an invalid link Actual: https://wiki.cac.washington.edu/ is affixed to the beginning of my link making it: https://wiki.cac.washington.edu/https:/washington.edu/calendar/trumba I can understand why the software thought that the "https:/" could have been a directory, but this has been confusing for some of our users. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-41519]. {panel} We noticed today that a link, where the https:// was mistyped and was missing the final slash, got redirected as if it were a directory on the local web server, instead of just being a broken link. Would it be better to leave it broken, or to repair the link, instead of prefixing the local server to it? Steps to reproduce: 1. Edit this page: https://wiki.cac.washington.edu/pages/viewpage.action?pageId=72219641 2. Insert a mistyped link: http:/washington.edu/calendar/trumba 3. Click Save 4. Go visit your link and see where it goes. Expected: 1. Link would be "fixed" and extra / would be added after the http:/ so the link would go to its intended destination or 2. Link would go to broken link that I typed in or 3. I would have been notified after step 2 (or possibly after step 3) that I entered an invalid link Actual: https://wiki.cac.washington.edu/ is affixed to the beginning of my link making it: https://wiki.cac.washington.edu/https:/washington.edu/calendar/trumba I can understand why the software thought that the "https:/" could have been a directory, but this has been confusing for some of our users. |