Hi DK - and many thanks for your response.
It never ceases to amaze me that in this field of endeavour we are all constantly learning and no one person can know it all. The other thing that also amazes me is that when I make a mistake, I can keep making that same mistake. Last night I was relieved to find that I am not alone in this when I came across a situation in another forum where someone kept going down the same rat hole and it is not until another pair of eyes appear on the scene that the error becomes a glaring beacon!
So, to begin, let me come to the OFF TOPIC question: The sites concerned are built with PyroCMS which is based on Codeigniter. So, no filenames are present in the URI as the various controllers in the MVC structure manage the routing of requests and responses.
Next - the mistake I kept repeating was that I kept considering that /accommodation plus the query string, were the URI. On reading your reponse DK, I realised this is an error and that there is the URI (eg: accommodation on one hand and stay on the other), and attached to the URI is a different animal called a query string. So, thanks for the jog!
OK, so now, some more details are called for so I apologise in advance for not revealing the full extent of what we need to accomplish here (if that is at all possible).
The business concerned has gone through a re-branding process - hence the new site. In addition to this, both sites rely on a 3rd party provider for some of the data that gets presented on the sites. This data is pulled in via iFrames.
Now, to further complicate matters, the retrieval of this data from the other provider takes time. It was decided by the client that on the new site, instead of dragging this data in, they would have their own local copy of some of that data - which meant double handling, but provides a better experience for the end user.
At oldsite.com/accommodation a listing of all accommodation establishments gets pulled in via the iFrame as the default process.
However, at newsite.com/accommodation, the local copy of the data gets presented without the need to resort to the iFrame.
The other thing to consider is that there is still a need to be able to provide detailed information from the other provider and that is being done via the query string appended to /accomodation on the oldsite.com. I have no idea how this can happen, all I know is that it does.
With the introduction of the new site, it was decided to use an alternative address for the delivery of the detailed information, hence the /stay uri has been adopted for that and this now is the address used for the iFrame data…
So, the critical thing here is to be able to redirect visits to the oldsite.com/accommodation-plus the query string - to newsite/stay-plus the query string. If users visit oldsite.com/accommodation - we do not want them to be re-directed to newsite.com/stay. In fact, the accommodation nav links on oldsite.com have been changed in the CMS so that they now point to newsite.com/accommodation.
I hope all this is making sense. Thanks for taking the time to read and offer your suggestions/conclusions.