Skip to content
This repository has been archived by the owner on Aug 25, 2024. It is now read-only.

Module corrently only supports HTTPS. It's worth exploring if adding HTTP support is practical for development environments. #26

Open
ArtisanByteCrafter opened this issue Nov 1, 2019 · 0 comments
Open

Module corrently only supports HTTPS. It's worth exploring if adding HTTP support is practical for development environments. #26

ArtisanByteCrafter opened this issue Nov 1, 2019 · 0 comments
Assignees
@ArtisanByteCrafter
Labels
enhancement New feature or request

Comments

@ArtisanByteCrafter
Copy link
Owner

Each cmdlet sets the TLS negotiation at a minimum of TLS 1.2. Obviously trying to connect over HTTP would not work in this case. There have been a few reports of people asking if they can connect to a test appliance w/o ssl configured, hence this issue.

It might not be practical at all, but I'm filing an issue anyway as a placeholder to look into it.
@ArtisanByteCrafter ArtisanByteCrafter self-assigned this Nov 1, 2019
@ArtisanByteCrafter ArtisanByteCrafter added the enhancement New feature or request label Nov 1, 2019
@ArtisanByteCrafter ArtisanByteCrafter changed the title Module corrently only supports HTTPS / TLS 1.2. It's worth exploring if adding HTTP support is practical for development environments. Module corrently only supports HTTPS. It's worth exploring if adding HTTP support is practical for development environments. Nov 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ArtisanByteCrafter ArtisanByteCrafter

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ArtisanByteCrafter