You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Is your feature request related to a problem? Please describe.
In the FAQ page for "Supported location hash properties" there's an example referencing a diagram located at a specific URL from a public GitHub pages site.
Assuming this error is related to redirection behavior for authentication to the private domain, the feature request to resolve access to private gitlab pages so that the example URL above does not result in a "File Not Found" error.
Describe alternatives you've considered
One potential alternative is to reference a specific gitlab branch or commit with the #A directive. That requires pointing to a particular branch, which is ok. I have a particular workflow that relies on information posted to gitlab pages being the "official" documentation, so I wanted the diagram access to be consistent with that.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In the FAQ page for "Supported location hash properties" there's an example referencing a diagram located at a specific URL from a public GitHub pages site.
However, "Error loading file: File not found" occurs when trying to access a private GitLab-pages domain with the same syntax (i.e. https://app.diagrams.net/#Uhttps%3A%2F%2Fmydomain.gitlab.io%2Fmyrepo%2Fmyfile.svg). I've verified that https://mydomain.gitlab.io/myrepo/myfile.svg is accessible if typed directly into my browser.
Describe the solution you'd like
Assuming this error is related to redirection behavior for authentication to the private domain, the feature request to resolve access to private gitlab pages so that the example URL above does not result in a "File Not Found" error.
Describe alternatives you've considered
One potential alternative is to reference a specific gitlab branch or commit with the #A directive. That requires pointing to a particular branch, which is ok. I have a particular workflow that relies on information posted to gitlab pages being the "official" documentation, so I wanted the diagram access to be consistent with that.
Additional context
N/A
The text was updated successfully, but these errors were encountered: