Skip to content
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

can not upload file to api route #58

Open
applemate opened this issue May 20, 2024 · 7 comments
Open

can not upload file to api route #58

applemate opened this issue May 20, 2024 · 7 comments

Comments

@applemate
Copy link

applemate commented May 20, 2024

with node-adapter I can upload file to api route

with svelte-adapter-bun I can not upload file to api route. Error: 403 forbidden

tested with the same file and size

to reproduce

create a brand new sveltekit app from command line

create an api route with POST request
create a +page.svelte in a normal route in src , in there you upload file to api route using fetch with post method.
it will fail.

@ptrxyz
Copy link

ptrxyz commented Jun 16, 2024

Can you provide a repository with a minimal demo app? @craigcosmo

@applemate
Copy link
Author

here is the repo

https://github.com/craigcosmo/mytron

@KyleFontenot
Copy link

KyleFontenot commented Jul 15, 2024

@craigcosmo In your reproduction, in file /src/lib/config.ts, doesn't look like you updated the dev urls:

let apiUrl: string =
  env == 'production'
  ? 'https://contron.vn/api/'
  : 'http://localhost:2233/api/'

Changing the dev url to 'http://localhost:9955/api/' gave me a success message.

@applemate
Copy link
Author

I mean it works on localhost, but not on any server, whether it's vercel or render.com

When I switched back to node apdater, the upload worked on servers.

@notramo
Copy link

notramo commented Oct 2, 2024

@craigcosmo, the origin checking has been changed lately, could you test if it still fails?

@applemate
Copy link
Author

This happened before the origin checking

@KyleFontenot
Copy link

My hypothesis is that origin-checking is not the issue, but more that there were problems with how Bun handled requests. In Bun 1.1.27 they seemed to have fixed it, so after upgrading Bun, I'd be curious if the problem remains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants