File Upload URLs
ManualWorks uses the following URLs for file uploads.
This list is based on ManualWorks 6.0.4. URLs can be added or removed in major or minor releases.
URL | Description |
|---|---|
/r/abbreviation_term/upload_excel | Uploads abbreviations from an Excel file |
/r/answer/upload_file/${id} | Uploads an attachment to an answer in the <Task> menu |
/r/create_chapter_from_markdown/upload/${id} | Creates chapters by dragging Markdown files onto the chapter list of a document |
/r/editor_print_image/upload/${id} | Uploads a print image in the editor |
/r/font/upload | Uploads a font file in the <Style | PDF Font> menu |
/r/file/upload | Uploads a file through the common upload function |
/r/file_explorer/change_file/${id} | Replaces a file in the <Resource | File> menu |
/r/file_explorer/upload | Uploads a file in the <Resource | File> menu |
/r/glossary/upload_terms | Imports a terms file in the <Resource | Glossary> menu |
/r/hyphenation_pattern/upload/${locale} | Uploads a hyphenation pattern file in the <Resource | Hyphenation Pattern> menu |
/r/image_explorer/upload | Uploads an image file in the <Resource | Image> menu |
/r/import_from_file/upload/${id} | Uploads a Word file and creates chapters from it |
/r/inline_image_explorer/upload | Uploads an image file in the <Resource | Inline Image> menu |
/r/newsletter_subscriber/upload_subscribers | Imports a subscriber file in the <Tool | Newsletter Subscriber> menu |
/r/software_update/upload | Uploads a software update file when the ManualWorks update server cannot be reached |
/r/static/upload/${id} | Uploads a file in a static document |
/r/task/upload_file/${id} | Uploads an attachment in the <Task> menu |
How File Uploads Work
ManualWorks sends the file selected in the web browser to the server as is with XMLHttpRequest.
ManualWorks uses XMLHttpRequest only for file uploads. Other operations use the Fetch API. Therefore, at the network level, requests made with XMLHttpRequest can be classified as file uploads. However, the following send file content to the server without XMLHttpRequest, so you cannot identify all file uploads from XMLHttpRequest requests alone.
Pasting an image from the clipboard into the editor: the image data (base64) is sent to
/r/clipboardwith the Fetch API.Uploading a Markdown file in the editor: the file content is sent to
/r/upload_markdown/upload/${id}with the Fetch API.Inserting or pasting an image in the task and answer editors: the image data is included in the body and sent with the save request.
Uploading an image from an MCP client: it is sent to
/r/mcp_uploaddirectly, not through the web browser.
However, Monaco Editor, an open-source library used by ManualWorks, can use XMLHttpRequest. Its path is /resource/monaco_editor/.