Proxied Installation

Whatever domain or URL that is visible to the world is what would be used everywhere. Outside world is not aware of whether the server proxies the request back to another server or serve the request directly. Whatever domain or URL you want in the front for the world to see is what should be setup on the server that interacts with the world.

If I have misunderstood your setup or usecase, please explain with example domains such as example.com, example.org etc

Okay I think you got the basics, how some of my description was lacking, when I said in a framework, the pages are pulled into a relevant url using an iframe.

Hopefully making it clearer, the wordpress blog is hosted at :

exampleA.com/

Then, the pages are made public at

exampleB.com/features/

However just to complicate things, exampleA.com/blogpost1 is on the public page exampleB.com/features/blogpost1 inside an iframe.

In an ideal world, the admin dashboard would still be exampleA.com

I think I explained that all this time.

Oh so you want the links in the content to be exampleB.com/features/something but they are obviously of exampleA.com/something, is that right? Or you want the user to navigate to exampleB.com/features/something when clicked? Or something else?

Either way, its not going to be possible with iframe embedding. This is a very unusual setup. Can you clarify what’s really the reason behind the setup this way? That way I would be able to make better recommendations.

I can parse out the links in the proxy, if I need to, not ideal but it is doable, however any automated social media posts or pings will also have the wrong address.

The existing site has a look\feel etc. and it is required that the blog fits into the existing framework to present the same look\feel. I’m open to other suggestions, although it is felt that the iframe offers better security between the wordpress site, and the existing site. I am not convinced by that though, so am happy to argue that one away if their is a better solution than iframes.

I still don’t understand why the WordPress install can’t reside in just a subdirectory “features” under exampleB.com with its url as exampleB.com/features?

Whatever styles you need the pages to have, can be done on a theme level.

And if there is still something that’s forcing you to use this setup, it would be better if you were serving pages without the iframe, after doing whatever HTML manipulation you need to do. This would make it appear as HTML coming from just exampleB.com/features but I would say this, this is unnecessarily complicated without any good reasons for doing so, atleast from what I have understood so far.

Internal politics dictates that we don’t install 3rd party apps on the server, even though we proxy it from elsewhere. We could possible proxy it directly to to the site rather than an iframe, but then we would have to duplicate the existing site look and feel along with header and footer links, rather than fit into it.

I still don’t understand why the WordPress install can’t reside in just a subdirectory “features” under exampleB.com with its url as exampleB.com/features?

Its still possible to do so without changing what’s what on which server. exampleB.com/features sitting on server interacting with the world will proxy back to server which runs WordPress but also has exampleB.com as the host being requested & URL of that install. And it would respond with whatever, just spit out the html as it is and it should all be better than manipulating things?

Yes, I just then have to design a theme that mimics the main site, including headers/footer and a side menu. I know it’s not impossible, but combined with arguing about the iframe not really adding any security. I was hoping there was a way of convincing the social media plug ins to give the public address, but I guess it’s not going to be that easy.

Thanks for your help and time anyway.