-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
API V3 #163
Conversation
Co-authored-by: Mrgaton <[email protected]>
Co-authored-by: Ivan Gabaldon <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
# Conflicts: # .github/workflows/release.yml # .github/workflows/security.yml # .github/workflows/test.yml
# Conflicts: # .github/workflows/release.yml # .github/workflows/security.yml # .github/workflows/test.yml # biome.json # bun.lockb # package.json
# Conflicts: # .github/workflows/release.yml # .github/workflows/security.yml # .github/workflows/test.yml
# Conflicts: # src/document/compression.ts # src/document/crypto.ts # src/endpoints/v1/access.route.ts # src/endpoints/v1/accessRaw.route.ts # src/endpoints/v1/publish.route.ts # src/endpoints/v2/access.route.ts # src/server.ts # src/server/endpoints.ts # src/types/Document.ts # tsconfig.json
Se podrá aceder a documentos con contraseña por query? |
No sé qué tan seguro puede ser esto, el navegador guarda en el historial toda la URL incluido la query |
# Conflicts: # bun.lockb
Tampoco es que el documento sea super secreto, aparte así es mas difícil para acceder por ejemplo por query y no puedes acceder directamente por URL. |
# Conflicts: # bun.lockb # src/server.ts
# Conflicts: # src/endpoints/v1/access.route.ts # src/endpoints/v1/accessRaw.route.ts # src/endpoints/v1/remove.route.ts # src/server.ts
|
PR obsoleto, seguir en #189 |
Para hacer
Para evaluar