POST /documents/upload generates incorrect URL #161
Milestone
Comments
mfriesen
added a commit
that referenced
this issue
Aug 2, 2023
mfriesen
added a commit
that referenced
this issue
Aug 14, 2023
* #130 - Feature: Added PUT/PATCH /documents/{documentId}/tags to allow adding/updating multiple tags to a document at once * #131 - Feature: Added POST /documents/compress to create a ZIP file of multiple document's contents. * #133 - Feature: Added PATCH /documents/tags to allow adding tags to documents based on tag search criteria * #138 - Bug: Added validation for reservered tag keys when using POST /documents * #144 - Bug: DELETE /indices/folder return 500 when invalid siteId is used * #145 - Feature: Added Typesense support to API GET documents/{id}/fulltext * #150 - Bug: Renamed module 'fulltext' to 'opensearch' * #151 - Bug: Documentation for POST /documents/upload, missing contentLength * #158 - Bug: Improved Actions API validation * #159 - Feature: API Keys added READ / WRITE / DELETE permissions * #161 - Bug: POST /documents/upload generates incorrect URL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using a POST /documents/upload?siteId=default a incorrect S3 url is generated that causes the document to be saved in a incorrect location. All other siteId work fine, just not "default"
The text was updated successfully, but these errors were encountered: