Improve HTTPS support for client development#23
Merged
Conversation
jimenezz22
approved these changes
Jun 17, 2025
Contributor
There was a problem hiding this comment.
@kronosapiens I understand your point about adding the HTTPS certificate configurations to localhost. The problem is that we have a deployment in Vercel, and it would crash if these certificates were allowed. I'm going to merge your PR and configure this VITE file to work dynamically based on the environment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Controller requires HTTPS to connect to the client. This PR makes HTTPS the default behavior for local development.
npm run mkcert