Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / battlejj/express-force-ssl issues and pull requests
#32 - Adding support to set this header
Pull Request -
State: open - Opened by root-at-yourFridge over 3 years ago
#31 - Deprecated message using express 4.16.3
Issue -
State: closed - Opened by joetidee almost 6 years ago
- 3 comments
#30 - feat: upgrades node requirement to use builtin Object.assign method
Pull Request -
State: open - Opened by JaKXz about 6 years ago
- 2 comments
#29 - Heroku SSL error
Issue -
State: closed - Opened by jwelton over 7 years ago
- 3 comments
#28 - fix syntax error in readme
Pull Request -
State: closed - Opened by gswalden about 8 years ago
- 1 comment
#27 - Updated custom ssl port example to utilize v0.3.0 config options.
Pull Request -
State: closed - Opened by Alfredo-Delgado over 8 years ago
- 1 comment
#26 - Issues#19,#25
Pull Request -
State: closed - Opened by battlejj almost 9 years ago
#25 - Module should not trust x-forwarded-proto by default
Issue -
State: closed - Opened by sebastiang almost 9 years ago
- 3 comments
#24 - Export factory instead of a middleware function and other changes
Pull Request -
State: closed - Opened by fatfisz almost 9 years ago
- 3 comments
#23 - Only certain pages SSL
Issue -
State: closed - Opened by christiansr85 almost 9 years ago
- 2 comments
#22 - Further fix for issue 20.
Pull Request -
State: closed - Opened by battlejj about 9 years ago
#21 - Replace req.url with req.originalUrl to fix trim bug
Pull Request -
State: closed - Opened by battlejj about 9 years ago
#20 - req.url gets modified by express next()
Issue -
State: closed - Opened by tatepostnikoff about 9 years ago
- 4 comments
#19 - Additional Options Support
Issue -
State: closed - Opened by battlejj over 9 years ago
- 4 comments
Labels: enhancement, question
#18 - Enable options on a per route basis
Issue -
State: closed - Opened by battlejj over 9 years ago
- 4 comments
Labels: enhancement, question
#17 - Add option to prevent redirects
Pull Request -
State: closed - Opened by cltatman over 9 years ago
- 9 comments
#16 - why not use 307 or 308 redirect?
Issue -
State: closed - Opened by ryanmeador over 9 years ago
- 4 comments
#15 - req is undefined
Issue -
State: closed - Opened by csernikmarton over 9 years ago
- 6 comments
#14 - Cleaning up tests.
Pull Request -
State: closed - Opened by battlejj over 9 years ago
#13 - express-force-ssl only redirects on default context
Issue -
State: closed - Opened by figui over 9 years ago
- 9 comments
#12 - Cleaned up X-Forwarded-Proto check, added tests
Pull Request -
State: closed - Opened by battlejj almost 10 years ago
#11 - Create Tests for Project
Issue -
State: closed - Opened by battlejj almost 10 years ago
- 7 comments
Labels: enhancement, question
#10 - Add testing framework
Issue -
State: closed - Opened by ronco almost 10 years ago
- 1 comment
#9 - Protect against undefined error on header not set
Pull Request -
State: closed - Opened by ronco almost 10 years ago
- 3 comments
#8 - TypeError when proxy header not found
Issue -
State: closed - Opened by ronco almost 10 years ago
#7 - check 'x-forwarded-proto' for 'https' as well
Pull Request -
State: closed - Opened by ronco almost 10 years ago
- 4 comments
#6 - Better readme
Pull Request -
State: closed - Opened by battlejj almost 10 years ago
#5 - Recommendations for a clearer README.md
Issue -
State: closed - Opened by emilbayes almost 10 years ago
- 4 comments
#4 - Use HTTP code 301
Pull Request -
State: closed - Opened by emilbayes almost 10 years ago
- 1 comment
#3 - Example to override https port should be app.set(..) not app.use(..)
Issue -
State: closed - Opened by ElwoodPDowd almost 10 years ago
- 1 comment
#2 - Fix mismatching variable name
Pull Request -
State: closed - Opened by fabslab almost 11 years ago
- 1 comment
#1 - Avoid "Error: Can't set headers after they are sent."
Pull Request -
State: closed - Opened by timshadel about 11 years ago
- 4 comments