Using https works fine for me, in fact, I redirect all the http request to https with the same uri, so maybe we don't have to say "no ssl", what do you think?
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dehydrated-io/dehydrated/pull/159
**Author:** [@PeterDaveHello](https://github.com/PeterDaveHello)
**Created:** 3/2/2016
**Status:** ✅ Merged
**Merged:** 3/8/2016
**Merged by:** [@lukas2511](https://github.com/lukas2511)
**Base:** `master` ← **Head:** `patch-2`
---
### 📝 Commits (1)
- [`dc40813`](https://github.com/dehydrated-io/dehydrated/commit/dc40813cca52ca591f3611de985754eb1f976a0b) Update README.md
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -1)
</details>
### 📄 Description
Using https works fine for me, in fact, I redirect all the http request to https with the same uri, so maybe we don't have to say "no ssl", what do you think?
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/159
Author: @PeterDaveHello
Created: 3/2/2016
Status: ✅ Merged
Merged: 3/8/2016
Merged by: @lukas2511
Base:
master← Head:patch-2📝 Commits (1)
dc40813Update README.md📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
README.md(+1 -1)📄 Description
Using https works fine for me, in fact, I redirect all the http request to https with the same uri, so maybe we don't have to say "no ssl", what do you think?
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.