Feat add https support #37
Draft
Conversation
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
This fixes CORS Errors, To Query To Appropriate Backend Based Of The Current Protocol (Http, Or Https)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The deployment also supports now "https" at:
The "http" URLs of http://nextstep.theworkpc.com:1785 and http://backend.nextstep.theworkpc.com:1785 are still available but maybe they should be removed, because the backend url is "hard-codedly" written in the "Posts" and "Comments" with the old "http" url, and could not be retrieved correctly when viewing the frontend in "https" because of CORS errors:
Still having CORS issues when accessing the backend from the frontend.