Preface:
We have written some software that allows our users to embed the content of many of their webpage building tools directly into their websites. For instance, our clients use a medley of Landing Page or "Funnel" building tools. Many of these tools are pretty antiquated and don't have a native way to bring that content elsewhere, and our clients don't like to send users to our-client.some-landing-page-builder.com/landing-page
.
We have developed some software that will fetch the content at our-client.some-landing-page-builder.com/landing-page
, do some work on the action
, src
, etc. attributes (some of these tools use relative URLs and wouldn't change them to absolute for us), and then it gets embedded directly into their website, our-client.com/landing-page/
. It uses an optional cache or microcache to make sure that the content is fresh, and it has been working excellently for years.
The Problem:
When a user visits our-client.com/landing-page/
, and the software makes a request to the content on the Landing Page builders, the request that is sent belong to the our-client.com
and not the user that visited the site. For most of our clients, this isn't an issue.
The Question:
We have one client in particular that is asking if there's a way to send that user's request headers from our-client.com
to some-landing-page-builder.com
?