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
The CLI message should output something as: "Running on https:localhost:8080" when the server is using a custom entry point that provides a valid securityContext.
The text was updated successfully, but these errors were encountered:
Hi @alestiago , I ran thorugh a lot of files and figured out that we just have to know whether this is a secure or not . The final thing that we have to change is dart_frog_cli . But How can we get to that the user has provided the secuirtyContext and it is good and working . I have files like daemon_server.dart , i am just trying to look how the port and ip address from main are passing to the server . May you please help where to start with this.
@dhruvpatidar359 Writing a detailed guide to this would be as long as tackling the solution, I can summarize:
The condition to show the correct protocol in the message should come from the existence of a secure context on the running server, this can be defined in the hook of the devserver brick.
This condition has to be communicated back to the CLI somehow.
Description
When running a Dart Frog server that uses a securityContext the CLI outputs an erroneous message.
Upon secure serving the output should be "Running on https://..." instead of "Running on "http://...".
Steps To Reproduce
server_chain.pem
andserver_key.pem
from this Dart tutorial and save onsample/.dart_frog/certificates
Expected Behavior
The CLI message should output something as: "Running on
https:localhost:8080
" when the server is using a custom entry point that provides a valid securityContext.The text was updated successfully, but these errors were encountered: