404 link in docker-compose related why-is-ssrf_proxy-needed

[htynkn]

Self Checks

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

Provide a description of requested docs changes

https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml#L297

Link https://docs.dify.ai/learn-more/faq/self-host-faq#id-18.-why-is-ssrf_proxy-needed is 404

[dosubot[bot]]

@htynkn Hello! I'm here to help you with any bugs, questions, or contribution-related matters.

I found a similar closed issue regarding a 404 link in the documentation for the ssrf_proxy server. The correct URL for the ssrf_proxy server documentation in the docker-compose.yaml file should be:

# ssrf_proxy server
# for more information, please refer to
# https://docs.dify.ai/getting-started/install-self-hosted/install-faq#id-16-why-is-ssrf_proxy-needed
ssrf_proxy:
  image: ubuntu/squid:latest
  restart: always
  volumes:
    # pls clearly modify the squid.conf file to fit your network environment.
    - ./volumes/ssrf_proxy/squid.conf:/etc/squid/squid.conf
  networks:
    - ssrf_proxy_network
    - default

This link points to the section about the "ssrf_proxy" server in the self-hosted installation FAQ, explaining why it is needed ^[1].

Additionally, the SSRF proxy is needed in the docker-compose.yaml file for the Dify project to prevent SSRF (Server-Side Request Forgery) attacks. This is achieved by configuring a proxy for all services that might cause SSRF attacks and forcing services like Sandbox to only access external networks through the proxy, ensuring data and service security ^[2][3].

To continue talking to Dosu, mention @dosu.