fatedier
For proxies of type `tcp`, frp does not modify any transmitted content. Generally speaking, if issues arise, they are mostly related to application layer logic, such as restricting access by...
FTP should no longer be the recommended protocol or tool.
Could you provide relevant documentation or examples from other projects? Also, please add an end-to-end (e2e) test case to ensure existing functionality is not affected.
> @fatedier I think it's safe to wrapper the `handler` with `h2c` if we don't want to introduce new optional parameter Can the code be modified in this way? And...
A quick look shows that server-side support for h2c seems compatible and can be directly added. However, proxying to the backend using http2.Transport is incompatible. Perhaps we could split the...
The better approach is to submit an issue first, engage in a discussion, reach a consensus, and then submit the code.
I'd prefer not to introduce new optional parameters. Maybe we can support this functionality transparently so users don't need to make any changes.
This usually depends on your network conditions and bandwidth.
The ACL feature is in the plan.
You could try forwarding more related ports—it seems like this might be an application-layer issue.