Skip to content
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

Added support for running the webpack dev server in ssl mode #2089

Closed
wants to merge 13 commits into from
Closed

Added support for running the webpack dev server in ssl mode #2089

wants to merge 13 commits into from

Conversation

sbaramov
Copy link
Contributor

@sbaramov sbaramov commented Sep 13, 2016

Added support for running the webpack dev server in ssl mode through 'ng serve' command. The command options --ssl, --ssl-key, and --ssl-cert are used to configure the server.

Fixes #1576.

…ng serve command. The command options --ssl, --ssl-key, and --ssl-cert are used to configure the server. This patch is related to issue #1874 and #1576.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@sbaramov
Copy link
Contributor Author

i signed it

On Tue, Sep 13, 2016 at 4:12 PM googlebot notifications@github.com wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll

verify. Thanks.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2089 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ7-PfRzuYwimMKr9YG48-bNWn5_zy2uks5qpwOcgaJpZM4J8F5E
.

@googlebot
Copy link

CLAs look good, thanks!

Copy link
Contributor

@hansl hansl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also add an e2e test. You can store a dummy key in github.

@@ -17,6 +17,9 @@ interface IWebpackDevServerConfigurationOptions {
headers?: { [key: string]: string };
stats?: { [key: string]: boolean };
inline: boolean;
https: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This field should probably be optional.

@sbaramov
Copy link
Contributor Author

@hansl , I am sorry but I do not see the e2e test for serve-webpack.ts. Can you give me some pointers?

…3093d147cb26c83bb68695' into pull-request-webpack-ssl
@filipesilva
Copy link
Contributor

@sbaramov the closest test I can find is the one for the proxy functionality, it also needs a file and does a request. See ./tests/e2e/tests/misc/proxy.ts

@zackarychapple
Copy link
Contributor

This looks like a great feature, I would only request that you add another param for certificate authority. Both GoDaddy and Symantec have a ca that can go with the crt and key.

@sbaramov
Copy link
Contributor Author

sbaramov commented Oct 4, 2016

@filipesilva Thanks, the test is implemented now.

@Brocco Brocco assigned Brocco and unassigned filipesilva Oct 14, 2016
Copy link
Contributor

@Brocco Brocco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests and all look good

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@Brocco
Copy link
Contributor

Brocco commented Oct 19, 2016

@sbaramov PR looks fine, just rebased it for merging & cla got out of whack, can you please comment again that you've signed it?

@sbaramov
Copy link
Contributor Author

Yes i have signed the CLA.

@Brocco
Copy link
Contributor

Brocco commented Oct 19, 2016

@sbaramov apparently losing the CLA signing is not something we can recover from on this PR, can you please submit the same code in a new PR?

Just tag me in it and I'll take a look. Take care to rebase prior to pushing the new one too, please.

@sbaramov
Copy link
Contributor Author

Closing the pull request in favor of #2792 because the CLA did not work here.

@sbaramov sbaramov closed this Oct 20, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Errors using Angular-CLI locally with --ssl true
6 participants