Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

dispatcher Error

Avatar

Former Community Member

Hi Guys,

I am getting a Strange error in the Apache Dispatcher Logs . We have an Apache server in front of  CQ Author. 

The html Page renders properly directly from Author IP but it throws a 500 Error when accessed from Apache.

Following is the Error message in Dispatcher logs

>>

Error while sending body: Broken pipe
"GET /content/test/home.html" 500 36103 1186ms

<<

 

Has anyone encountered this error before?.

 

Thanks,

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Thanks Sham and Ove for your Help.

We identified the issue. Our Author Apache server was on HTTPS and the Web Service Call was being made on HTTP, So browsers were blocking the requests. We found the solution that either Force HTTP for that Path on Apache or change the Web service URL to load on HTTPS.

Thanks Again

View solution in original post

6 Replies

Avatar

Level 6

I have seen the Broken pipe problems when the virtual host and the Author is not aligned. The Author needs to "think" that it is the same as the Dispatcher.

What Dispatcher version do you use?

What Apache HTTPD server?

How is your VHOST configured?

How does the author_dispatcher_new.any looks like?

 

/Ove

Avatar

Level 10

This indicates the client closed the connection. Per your description client is Apache. check apache configs & network. 

Avatar

Former Community Member

Actually Page is loading properly but it seems like some Component (Which makes call to a GSA) of the Page is not loading fine and hence we are seeing 500 error in the Logs. Apache version is 2.2.15 and Dispatcher is 4.0.9

 

Thanks,

Avatar

Correct answer by
Former Community Member

Thanks Sham and Ove for your Help.

We identified the issue. Our Author Apache server was on HTTPS and the Web Service Call was being made on HTTP, So browsers were blocking the requests. We found the solution that either Force HTTP for that Path on Apache or change the Web service URL to load on HTTPS.

Thanks Again

Avatar

Level 8

Regardless of whether it would fix your current issue, your Dispatcher version is pretty old....consider updating to the current version (4.1.7) to benefit from bug fixes and new features https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher.html

scott

Avatar

Former Community Member

Thanks Scott for sharing this Useful Link. I will check this Out.