docs(plnkrOpener): open plnkr.co with HTTPS #14445
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Plnkr should be opened via HTTPS instead of HTTP to supress warnings about an insecure connection
|
CLAs look good, thanks! |
1 similar comment
|
CLAs look good, thanks! |
Plnkr should be opened via HTTPS instead of HTTP to supress warnings about an insecure connection Closes #14445
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs update
What is the current behavior? (You can also link to an open issue here)
Currently, plnkr gets opened with an unencrypted HTTP-connection. As the AngularJS-website redirects all users from HTTP to HTTPS, Firefox complains about the redirection (and the sending of data from an encrypted to an unencrytped site) to plnkr with a warning pop-up.
What is the new behavior (if this is a feature change)?
Examples are no getting opened using a HTTPS connection.
Does this PR introduce a breaking change?
no
Please check if the PR fulfills these requirements