New cache header to allow/disallow for 203 headers which can cause some issues with Google


by browsing to here

And adding a post URL to validate results in

This really needs to be fixed for any clients or users who intend to use Social Media to post to Google+, works fine with Facebook but Google+ and W3C complain big time.


Luis Majano
October 22, 2013, 4:30 PM

Andrew, they have it wrong:

203 just indicate success but ccontent delivered from a third party (The
Cache). It is equivalent to a 200.

Luis Majano*
Ortus Solutions, Corp

ColdBox Platform:
ContentBox Platform:
Linked In:
Social: | | |

Andrew Scott
October 22, 2013, 4:36 PM

Luis, I hear what you are saying. But non-authoritative means that the content is not mine, Google+ doesn't like content from 3rd parties by the looks of it.

If it is coming from a cache is it actually considered, from a 3rd party?

Andrew Scott
October 22, 2013, 4:51 PM

And if I comment out the header 203 you set, Google+ works like a charm again.

Andrew Scott
January 20, 2014, 12:10 AM

Is there any reason why this hasn't been fixed? The fix is simple, remove the http header being set to 203 as you are now.

I know you don't or haven't setup your Google+ account to be an author at the moment, but why are you punishing us who has?

I am sick and tired of having to remove certain things from ContentBox, because you can't be stuffed fixing some simple little things like this.

Andrew Scott
January 20, 2014, 2:31 AM

I should also point out what the W3C says about HHTP status code 203

I take that, as well as Google must take it the same way. It appears that Googel+ and the Author program they offer, sees 203 as being written by someone else. Since ContentBox this has been changed, Google now sees my content as not written by me and penalises me in the rankings etc.

Serioulsy Luis this needs to be fixed and should have been fixed when it was raised.



Luis Majano


Andrew Scott




Fix versions