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

fix(nextjs): additional experimental HTTPS options #23334

Merged
merged 1 commit into from
May 17, 2024

Conversation

jaysoo
Copy link
Member

@jaysoo jaysoo commented May 13, 2024

There are three additional flags if user wishes to generate their own key, cert, ca files rather than the auto-generated ones by Next.js.

Current Behavior

Cannot pass additional CLI options.

Expected Behavior

Can pass additional CLI options for custom files.

Related Issue(s)

Closes #23331

@jaysoo jaysoo requested review from a team as code owners May 13, 2024 13:41
@jaysoo jaysoo requested a review from ndcunningham May 13, 2024 13:41
Copy link

vercel bot commented May 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview May 17, 2024 6:35pm

@jaysoo jaysoo force-pushed the feat/nextjs-https-params-23331 branch from 8d49da1 to e66a98e Compare May 17, 2024 18:23
@jaysoo jaysoo merged commit 53345f2 into master May 17, 2024
6 checks passed
@jaysoo jaysoo deleted the feat/nextjs-https-params-23331 branch May 17, 2024 18:50
FrozenPandaz pushed a commit that referenced this pull request May 21, 2024
There are three additional flags if user wishes to generate their own
key, cert, ca files rather than the auto-generated ones by Next.js.

## Current Behavior
Cannot pass additional CLI options.

## Expected Behavior

Can  pass additional CLI options for custom files.

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Closes #23331

(cherry picked from commit 53345f2)
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2024
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.

None yet

2 participants