Secure page links sometimes include unexpected content in their path (e.g. /content)

Authors have noticed that links on secure pages (those with -pw in their name) sometimes include unexpected content in their path, such as /content;
e.g. https://www.buffalo.edu/content/www/your_site/... instead of just https://www.buffalo.edu/your_site/...

A previous Known Issue also addressed issues on secure pages -- see Secure Page Does Not Show Site Navigation.

This issue can extend to many or all links on the page, including buttons in the header, top navigation, and lists or other links on the main page.

We will continue to triage this issue. The only workaround is to use absolute URLs (https://...) instead of a relative path.