-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: boot all development servers with SSL by default #685
Comments
I got an error with the I changed the source as Has anyone else tried this? Maybe it's on my end. |
I just tried and it works, maybe it's because you're running on Windows? IDK why it's like that but could you please try in the terminal? # go to pasaport directory (full path: monorepo/apps/pasaport)
cd /monorepo/apps/pasaport
# install concurrently to run multiple commands concurrently
npm install -g concurrently
# run 'npm run dev' and 'npx local-ssl-proxy --target 3001 --source 9001' concurrently
# ! THIS ENSURES THAT PORT '9001' IS AVAILABLE !
concurrently "npm run dev" "npx local-ssl-proxy --target 3001 --source 9001"
# if you do not have wget you can install
winget install -e --id JernejSimoncic.Wget
# try to fetch HTTP
wget http://pasaport.localhost.kamp.us:3001/
# try to fetch HTTPS
wget https://pasaport.localhost.kamp.us:9001/ --no-check-certificate If your output is different than mine, something doesn't work on Windows. If you can share your output we can look together. P.S. getting 404 error is fine since there is no Next.js entrypoint on root path (/) |
Describe the feature you would like to see added
As @emredevsalot mentioned here Twitch does only support secure (HTTPS) urls. To use Twitch auth strategy in Pasaport, we need to run Pasaport via SSL. Then, @usirin draw forth an idea to boot all development servers with SSL by default.
We can do that via local-ssl-proxy which grabs the source port and publishes new port with SSL. See example usage below:
If we do what I described above, we will able to access HTTP on port 3000 and HTTPS on port 3001 for example which makes things easier.
BREAKING CHANGE: If we are not writing cookies via
secure
property, we might get some troubles via accessing cookies from HTTPS websites? (might be the case, just FYI)See output below:
cc/ @emredevsalot @usirin @gurkanguray
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: