Scraping WebHelp content
Posted: Fri Jun 10, 2016 6:18 pm
Hi,
I am getting ready to share the documentation generated using Oxygen WebHelp with a client. This content is highly sensitive and needs to be shared using some form of access control. We are toying with the following idea in order to simplify the access control:
- Store the generated webhelp content on an internal server.
- Provide a link to the generated webhelp content from within a pre-existing system that our clients use and which has access control via login.
- The code behind for this link will read from our internal server, pull down the code for the webhelp webpage and render it within the pre-existing system.
This works fine for the HTML pages but falls over when using the search functionality.
I was wondering if anyone has experience with this challenge that they can advise on?
Thanks in advance,
Ann
I am getting ready to share the documentation generated using Oxygen WebHelp with a client. This content is highly sensitive and needs to be shared using some form of access control. We are toying with the following idea in order to simplify the access control:
- Store the generated webhelp content on an internal server.
- Provide a link to the generated webhelp content from within a pre-existing system that our clients use and which has access control via login.
- The code behind for this link will read from our internal server, pull down the code for the webhelp webpage and render it within the pre-existing system.
This works fine for the HTML pages but falls over when using the search functionality.
I was wondering if anyone has experience with this challenge that they can advise on?
Thanks in advance,
Ann