Background: My client is using a proxy server to point to the production environment of the project. So for example their deployment is at https://messyurl.com, but their proxy server is routed to display at https://niceurl.com.

What I did: I set the siteUrl config field to https://niceurl.com, which successfully rendered niceurl.com links throughout all the templates. Cool. But when going to niceurl.com/admin, it redirects me to messyurl.com/admin. I thought I could solve it by adding the baseCpUrl config variable to be set to https://niceurl.com, but that made it so that I got a 404 when visiting https://niceurl.com/admin.

Any ideas why my cp is refusing to cooperate here? The client actually doesn't mind that the CP is at messyurl.com, but the thing they don't like is the entry preview is broken because of cross-domain stuff due to the url conflict.

  • It sounds like your client's proxy server isn't configured all the way. How is your client running the proxy server? I'm guessing their proxy is also doing caching/etc with it? If that's the case, they should be grabbing requests they can't serve including authentication an CP requests and relaying them back. Jan 7 at 22:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.