Spring boot 针对反应式Spring Boot WebFlux应用程序的NGINX设置

为了更好地理解反应式编程，我创建了一个小应用程序，它有两个端点：POST和get。POST方法将一些数据保存到MongoDB Atlas，GET方法从DB返回数据

工作流：通过浏览器获取请求-->通过curl发布一些新数据-->新数据将显示在浏览器中

工作流在本地工作，但只要我在混合中添加NGINX，工作流就会停止工作。不显示任何数据，一段时间后将终止连接

我的控制器：

    @GetMapping(value = "mda", produces = MediaType.APPLICATION_STREAM_JSON_VALUE)
    public Flux<ResponseData> getAll(){
        return repo.findBy();
    }

完成时：

---

/data端点包含POST和GET（NO@Tailable），它们在使用和不使用NGINX的情况下都可以工作。

能否请您共享当前的NGINX代理配置已添加配置：）能否请共享当前的NGINX代理配置已添加配置：）

   @Tailable
   Flux<ResponseData> findBy();

server {
    server_name example.com www.example.com;

    location / {
          try_files $uri $uri/ =404;
        }

    location /reactive/data {
        proxy_pass http://localhost:8081/data;
        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }

    location /reactive/mda {
        proxy_pass http://localhost:8081/mda;
        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;

        }   

    listen [::]:443 ssl; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = www.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    if ($host = example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    listen [::]:80;
    server_name example.com www.example.com;
    return 404; # managed by Certbot
}