A project for ensuring that https is used
See the codeA project for ensuring that https:// is used for everything except where it is not possible.
Today it is important for everything, including static sites, to be over https.
It can be difficult to switch to https:// and then to maintain using https://.
This project aims to help at both.
|
Note
| You can read more about the background of this project in the blog announcing nohttp. |
The project is split up into the following modules:
nohttp - the core project that allows finding and replacing http:// URLs
nohttp-cli - a thin wrapper around nohttp that allows running it from the command line
nohttp-checkstyle - provides checkstyle integration with nohttp
nohttp-gradle - provides Gradle integration with nohttp
samples - provides samples of using nohttp
How can I automate fixing my existing code?
Automation is beyond the scope of this project. However, you can easily automate fixing your existing code by scripting along with nohttp-cli. If you use GitHub, you can leverage GitHub APIs to automatically clone repositories within a set of organizations. You can use hub to automate sending Pull Requests.
What URLs need to be https?
See Thought Process
Are Allow Lists Supported
See Allow HTTP URLs
Java
84.8%
Kotlin
15.2%
A project for ensuring that https is used
See the codeA project for ensuring that https:// is used for everything except where it is not possible.
Today it is important for everything, including static sites, to be over https.
It can be difficult to switch to https:// and then to maintain using https://.
This project aims to help at both.
|
Note
| You can read more about the background of this project in the blog announcing nohttp. |
The project is split up into the following modules:
nohttp - the core project that allows finding and replacing http:// URLs
nohttp-cli - a thin wrapper around nohttp that allows running it from the command line
nohttp-checkstyle - provides checkstyle integration with nohttp
nohttp-gradle - provides Gradle integration with nohttp
samples - provides samples of using nohttp
How can I automate fixing my existing code?
Automation is beyond the scope of this project. However, you can easily automate fixing your existing code by scripting along with nohttp-cli. If you use GitHub, you can leverage GitHub APIs to automatically clone repositories within a set of organizations. You can use hub to automate sending Pull Requests.
What URLs need to be https?
See Thought Process
Are Allow Lists Supported
See Allow HTTP URLs
Java
84.8%
Kotlin
15.2%