I have a website running with couchcms which sends the form data to an other couchcms instance which serves as a backend. So one site only website (Page A) with a form, other site gathering the input data and creating cloned pages and doing other stuff (Page B).

So after sending a form from A to B, B processes the submitted data with the GPC tag and adds a cloned page with db_persist tag, then redirects the visitor to page A with a redirect tag.

This worked pretty well until I added HTTPS protocol to both pages and the form sends the data to https://B. Instead of redirecting back to page A, I get the empty page saying "Cheating?!".

When I point https://A to http:/B, then it workes again. But I would like to have it to work with secure target link to B as well, since otherwise the page is stated as non secure because of mixed secured and non secured links.

Anyone an idea how to wolve this?

Kind regards,
Olliwalli

[trendoman]

You get 'cheating' not on redirect, but on page save. Please verify that page indeed saves on B.

Hi trendoman

Yes, this is ok. It worked now for weeks, but does not work if I change the B site to https protocol: In the form of page A I changed the target from target='http://B/api.php' to target="https://B/api.php". After this change I get an "Cheating?!" message.

[cheesypoof]

The cheating message is exclusive to issues with access level, per a search of the code base - https://github.com/CouchCMS/CouchCMS/search?utf8=%E2%9C%93&q=cheating. I am constrained for time at the moment, otherwise I would try to provide a more helpful reply.

[trendoman]

Did you change config.php so B-couch knows about the change?

Problem solved!

It was not because of https, but because of changing the access level in one of the templates on localhost while being logged in and doing a lot of other changes the same time concerning https.