403 Error when using Frameless Output Mini-TOC - Part 1

Forum|Forum|1 year ago
July 15, 2024
2 replies
874 views

I am using RoboHelp 2022.4.179 to generate frameless output. The mini-toc links recently appear to have stopped working. When I click on a mini-toc link, I now get the error, "403: Forbidden: Access is denied: You do not have permission to view this directory or page using the credentials that you supplied." The error is not browser-specific. It occurs in both Chrome and Firefox. The system is truncating the mini-toc link (the portion after the pound symbol) to 15 characters. I think this truncation is causing the error. Is anyone else experiencing this issue? If yes, any known workarounds? Thanks!

This topic has been closed for replies.

Peter Grainge

Braniac

This thread is now locked. See https://community.adobe.com/t5/robohelp-discussions/403-error-when-using-frameless-output-mini-toc-part-2/td-p/14760146 for Part 2.

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Jeff_Coatsworth

Braniac

Haven't heard any reports of this before - was it working for you before? If so, what's changed? If not, is it working locally?

T

Timothy386187870sd3Author

Known Participant

It was working before. It is not now. I do not know what changed. I have attached two images. The first image shows the "In this Topic" link working. Notice that the URL shown at the top of the page is the URL to the topic and the URL shown at the bottom of the page is different but reflects the selected "In this Topic" link. The second image shows only one link, and it is the link that is shown at the bottom in the first image, not the link to the actual page that is shown in the top URL in the image where the link works. Curious. If I access the same topic in my local, I get the URL shown in the image below that does not work (file:///C:/FramelessOutput/240/Installation_Guides/Install_Guide_files/E-automate_Installation_Overview.htm#installing_e_au), but the link works as expected in my local. Guess that means it's not a truncation issue as I first suspected, but I am at a loss to explain/understand why it is not working in our production environment for newly generated outputs and is still working for older outputs (as well as for newer outputs in the local environment). Thoughts? Thanks!

Jeff_Coatsworth

Braniac

So it was working before on your webserver and now it's not? But the same output is behaving on your local? That kind of implies somebody has changed something on the webserver.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded