Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8200097
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T06:19:08+00:00 2026-06-07T06:19:08+00:00

NGINX currently runs as a proxy for our application, but recently I implemented comet

  • 0

NGINX currently runs as a proxy for our application, but recently I implemented comet and transfer-encoding: chunked. I realized that NGINX is messing with the response by not properly sending back the contents and instead buffering the Comet.

What are the appropriate settings to make this work? Will it need to be URI-specific to not interfere with other requests?

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T06:19:11+00:00Added an answer on June 7, 2026 at 6:19 am

    I was able to fix it with the following settings:

    proxy_buffering      off;
    proxy_connect_timeout       6000;
    proxy_send_timeout          6000;
    proxy_read_timeout          6000;
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

It seems that nginx does not support chunked requests well. But I'm trying to
I'm currently using Lighttpd on a VPS. Before that it was nginx, but I
I'm currently using nginx as a transparent proxy for apache. I would like to
I'm using nginx as a reverse proxy to apache/mod_wsgi and Django. Currently everything is
Im currently using Apache behind an Nginx Proxy which really works fine with one
I currently have one server with nginx that reverse_proxy to apache (same server) for
We are running nginx as a reverse proxy that forwards requests to a Clojure
When configuring nginx with a site that has ssl, the examples I find online
Our setup is standard nginx (ver 0.7.59) + thin upstream servers on Debian lenny.
I am building an intensive web application and currently all my URLs at the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.