403 Error when accessing self-hosted SeaTable via HTTP request in Dify 1.1.0

[zhushu11]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hello Dify Team,

I am encountering a 403 Forbidden error when trying to access my self-hosted SeaTable instance through an HTTP request node in Dify 1.1.0, which is deployed on the same self-hosted server. Interestingly, when I test the same request using Postman on my PC with identical URL and header settings, it works perfectly and returns the expected response. I would greatly appreciate your technical guidance to help resolve this issue.

Environment Information
Dify Version: 1.1.0 (self-hosted)
SeaTable Version: [Please specify your SeaTable version]
Deployment: Both Dify and SeaTable are deployed on the same self-hosted server.
Server OS: [Please specify your server OS, e.g., Ubuntu 20.04]
Network: Both services are accessible within the local network.

Dify HTTP Request Configuration
Method: GET
URL: https://your-seatable-domain.com/api/v2.1/workspace/1/dtable/System/access-token/
Headers:
accept: application/json
authorization: Bearer <your_bearer_token>
Response: 403 Forbidden

Postman Request Configuration (Successful)
Method: GET
URL: https://your-seatable-domain.com/api/v2.1/workspace/1/dtable/System/access-token/
Headers:
accept: application/json
authorization: Bearer <your_bearer_token>
Response: 200 OK with the expected data

Additional Details
The 403 error in Dify does not provide additional error messages, but I suspect it could be related to how Dify sends or processes the HTTP request.
I have confirmed that the Bearer token is valid and has the necessary permissions.
Since both Dify and SeaTable are on the same server, there should be no network-related restrictions between them.
Request
Could you please advise why the HTTP request from Dify results in a 403 error while the identical request from Postman succeeds? Are there any specific configurations or settings in Dify that I might need to adjust? Any suggestions or troubleshooting steps would be greatly appreciated.

Thank you for your support!

Best regards,

Yang Wang

2. Additional context or comments

No response