Accessibility

TechNote (Archived)

Errors when publishing in Breeze Presenter to a Breeze Server

Issue


When publishing to a Breeze Server through a firewall, some users may get errors stating that a 'Page cannot be displayed' or '500 internal server' error.

Reason


Many firewalls are configured to block requests that are not deemed RFC 2068 compliant. Some requests sent through the Presenter upload process are not RFC compliant and are therefore blocked by the firewall.

Solution


Users who encounter this behavior should first verify that they are connecting to the Breeze Server through a firewall. If so, then the firewall administrator should review the firewall logs to identify what, if anything, is being blocked.

They may see entries such as the following in the firewall log:

05/18/05 11:17:57 http-proxy[2646] [IPADDRESS:1529IPADDRESS:80] removing bogus HTTP header "GET /publish/content/sco/2?content-name=Presenter_Sample1&sco-id=41418880 HTTP/1.1"
05/18/05 11:17:57 http-proxy[2646] [IPADDRESS:1529IPADDRESS:80] Request denied: No URI found
05/18/05 11:04:55 http-proxy[13035] [IPADDRESS:1476IPADDRESS:80] removing bogus HTTP header "GET /common/meeting/launcher/openmeetingversioncheck.swf HTTP/1.1"
05/18/05 11:17:42 http-proxy[2646] [IPADDRESS:1527IPADDRESS:80] removing bogus HTTP header "GET /_a325331/loginPage/custom/styles/login_colors.css HTTP/1.1"

For Hosted Customers:

For hosted customers, the fix requires you to change your publishing location to https://admin.breezecentral.com. You can do this by following the steps below:

  1. Open a PowerPoint Presentation.
  2. Select Breeze > Publish.
  3. Select the Breeze Server tab if it is not selected.
  4. Click Change Server.
  5. Select the server and click Edit.
  6. Change the URL to: https://admin.breezecentral.com
  7. Click OK, then click Close.
  8. Click Publish.

You should now be able to publish without any problems.

For Licensed Customers:

The firewall administrator will need to reconfigure the firewall. To correct the issue, the firewall administrator should remove the HTTP service from the firewall, and add a more forgiving HTTP-proxied service that does a less in-depth analysis of HTTP headers.

AlertThis content requires Flash

To view this content, JavaScript must be enabled, and you need the latest version of the Adobe Flash Player.

Download the free Flash Player now!

Get Adobe Flash Player

Creative Commons License

Search Support

Document Details

ID:bba65ed0
OS:HP-UX
Linux
Mac OS (All)
Solaris
UNIX
Windows (All)
AIX
Browser:Chrome
Internet Explorer
Netscape
Opera
Safari
Firefox
Database:DB2
Informix
MySQL
Oracle
SQL Server
Sybase
MS Access

Products Affected:

acrobatconnect
presenter