Skip to content
This repository has been archived by the owner on Mar 17, 2022. It is now read-only.

Make express-sslify optional based on config #22

Closed
JaneJeon opened this issue Aug 19, 2019 · 0 comments
Closed

Make express-sslify optional based on config #22

JaneJeon opened this issue Aug 19, 2019 · 0 comments
Assignees
@JaneJeon
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
Configuration
Milestone
MVP

Comments

@JaneJeon
Copy link
Owner

Ideally, redirecting HTTP => HTTPS should be handled by the reverse proxy. But if you're directly exposing Heroku API, then you kinda need it.

This would also be a good time to look at the whole "reverse proxy" section of config
@JaneJeon JaneJeon added the enhancement New feature or request label Aug 19, 2019
@JaneJeon JaneJeon added this to the MVP milestone Aug 19, 2019
@JaneJeon JaneJeon self-assigned this Aug 19, 2019
@JaneJeon JaneJeon added this to To do in Configuration via automation Aug 19, 2019
This was referenced Aug 19, 2019
Open
Open
@JaneJeon JaneJeon added the wontfix This will not be worked on label Sep 5, 2019
@JaneJeon JaneJeon closed this as completed Sep 5, 2019
Configuration automation moved this from To do to Done Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@JaneJeon JaneJeon

Labels
enhancement New feature or request wontfix This will not be worked on
Projects
Configuration
  
Done
Milestone
MVP
Development

No branches or pull requests
1 participant
@JaneJeon