We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is possible.
https://docs.asciidoctor.org/asciidoc/latest/directives/include-uri/#caching-uri-content
Reading content from a URI is obviously much slower than reading it from a local file. Asciidoctor provides a way for the content read from a URI to be cached, which is highly recommended. To enable the built-in cache, you must: Install the open-uri-cached gem. Set the cache-uri attribute in the document. When these two conditions are satisfied, Asciidoctor caches content read from a URI according the to HTTP caching recommendations.
Reading content from a URI is obviously much slower than reading it from a local file.
Asciidoctor provides a way for the content read from a URI to be cached, which is highly recommended.
To enable the built-in cache, you must:
Install the open-uri-cached gem.
Set the cache-uri attribute in the document.
When these two conditions are satisfied, Asciidoctor caches content read from a URI according the to HTTP caching recommendations.
And these remote calls might be why in some rare situations, ascii_binder hangs forever.
ascii_binder
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is possible.
https://docs.asciidoctor.org/asciidoc/latest/directives/include-uri/#caching-uri-content
And these remote calls might be why in some rare situations,
ascii_binder
hangs forever.The text was updated successfully, but these errors were encountered: