You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I run my development environment using https as I deal with lots of OAuth providers that require https, even in development. It appears that the inngest development server discovers the service successfully when passing the url when starting the server npx inngest-cli@latest dev -u https://dev.mydomain.com:3000/api/inngest. This is great. However, when events are executed the POST to my dev server uses http instead of https.
Describe the solution you'd like
Ideally the inngest development server would post the requests to https if the url passed to inngest-cli -u is https.
It also took me a while to figure out this was the issue as the inngest dev server started fine and I was able to send events to it, they just never attempted to run. If https cannot be supported then having the dev server throw some sort of error would have saved me some time.
Describe alternatives you've considered
For the time being I've set up express to serve my app on both https(port 3000) and http(port 3001) and passing the http url when starting the server. This appears to work fine but is not ideal.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I run my development environment using
https
as I deal with lots of OAuth providers that require https, even in development. It appears that the inngest development server discovers the service successfully when passing the url when starting the servernpx inngest-cli@latest dev -u https://dev.mydomain.com:3000/api/inngest
. This is great. However, when events are executed the POST to my dev server useshttp
instead ofhttps
.Describe the solution you'd like
Ideally the inngest development server would post the requests to https if the url passed to
inngest-cli -u
is https.It also took me a while to figure out this was the issue as the inngest dev server started fine and I was able to send events to it, they just never attempted to run. If https cannot be supported then having the dev server throw some sort of error would have saved me some time.
Describe alternatives you've considered
For the time being I've set up express to serve my app on both https(port 3000) and http(port 3001) and passing the http url when starting the server. This appears to work fine but is not ideal.
The text was updated successfully, but these errors were encountered: