error 0 popup in section editor

Hi Craig,

This happens when the web server is misconfigured. What happens is when a script runs that produces no output, the server is outputting "0" to the screen. This is caught and interpreted as an error by CMS Builder.

Here is what you can do to demonstrate the issue. Create a new .php file and put in this code (only this code):

<?php exit; ?>

This script does nothing. However, if you view it in FireFox, you should see a 0 appear on your screen. You can forward that page on to your host. Although it is not a browser issue, other browsers tend to ignore it, so tell them to look at the page in firefox.

If they're unwilling to re-configure the server to correct this, you may want to consider moving hosts.

Hope this helps
Jason

Hey Jason, thanks.

Do you know what the configuration change it is that needs to be made?

thanks

Hi,

I've looked back through our records concerning this issue. The problem comes down to their server not complying with web standards.

Here are the technical details that you can forward along to them along with a url to the test page that has the <?php exit; ?> statement I sent you:

This server is sending an incorrect response according to RFC 2616.

The 0 displayed is not the PHP exit function's status code: it's what this server sends as content any time there is no content to be sent.

The server is sending a Content-Length of 0 and a message-body of "0", which is 1 byte long. This is contrary to the Content-Length of 0 it has sent. This is incorrect behaviour according to RFC 2616:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

"When a Content-Length is given in a message where a message-body is allowed, its field value MUST exactly match the number of OCTETs in the message-body."

Browsers will try to ignore conflicting information, rather than displaying an error. It so happens that Firefox decides to ignore the Content-Length header while Internet Explorer decides to ignore the message-body.

Please update your servers to adhere to w3 standards as described here:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

Hope this helps

Thanks Jason, that is great!