[GH-ISSUE #2943] [Feature Request] frp的http怎么设置跨域? #2347

Closed
opened 2026-05-05 13:30:52 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @xpxw on GitHub (May 17, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2943

Describe the feature request

host_Access-Control-Allow-Origin =*
host_Access-Control-Allow-Methods=*
host_Access-Control-Allow-Headers=content-type,token
host_Access-Control-Request-Headers=Origin, content-Type, Accept, token

header_Access-Control-Allow-Origin =*
header_Access-Control-Allow-Methods=*
header_Access-Control-Allow-Headers=content-type,token
header_Access-Control-Request-Headers=Origin, content-Type, Accept, token
都无效

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @xpxw on GitHub (May 17, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2943 ### Describe the feature request host_Access-Control-Allow-Origin =* host_Access-Control-Allow-Methods=* host_Access-Control-Allow-Headers=content-type,token host_Access-Control-Request-Headers=Origin, content-Type, Accept, token 和 header_Access-Control-Allow-Origin =* header_Access-Control-Allow-Methods=* header_Access-Control-Allow-Headers=content-type,token header_Access-Control-Request-Headers=Origin, content-Type, Accept, token 都无效 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:30:52 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Jun 17, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1158338978 --> @github-actions[bot] commented on GitHub (Jun 17, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
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#2347
No description provided.