[PR #311] [CLOSED] Make it clear that HTTPS can be password-protected too #4168

Closed
opened 2026-05-05 14:36:54 -06:00 by gitea-mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/fatedier/frp/pull/311
Author: @alecmev
Created: 5/6/2017
Status: Closed

Base: masterHead: master


📝 Commits (1)

  • 4baba2c doc: make it clear that https can be password-protected too

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 README.md (+1 -1)
📝 README_zh.md (+1 -1)

📄 Description

Had to look in the code to make sure that HTTPS can be password-protected.


🔄 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/fatedier/frp/pull/311 **Author:** [@alecmev](https://github.com/alecmev) **Created:** 5/6/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`4baba2c`](https://github.com/fatedier/frp/commit/4baba2c66575ea96b1146a2b8b1abbab752a2c9d) doc: make it clear that https can be password-protected too ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) 📝 `README_zh.md` (+1 -1) </details> ### 📄 Description Had to [look in the code](https://github.com/fatedier/frp/blob/3f9749488a2c485ebcb6f10b4a76b04b679205cc/src/models/server/server.go#L186) to make sure that HTTPS can be password-protected. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
gitea-mirror 2026-05-05 14:36:54 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#4168
No description provided.