We need help rewriting URL or proxying URL as to allow cross domain scripting and then using. We sign in automatically on a site where we what to change certain tags before showing it to the user, we want for instant "color certain tags in a different way", "add new forms connected to our database depending on page visited", and so on. Our programmer has tried different approches (listed below), he has made some progress but now he run out of ideas. We're trying to modify the content from a different domain where we have the script hosed, before showing it to the user. He has used these methodologies but now he's stuck: 1. Curl write the page into a test file and then read this page and modify. With this step, if I try to access inner page (after authentication) and try to read DIV tag for modifying its properties it gives me 302 exception with adress tag - and value - "Apache/2.2.6 (Unix) DAV/2 mod_ssl/2.2.6 OpenSSL/0.9.8e PHP/5.2.5 mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.7 Server at localhost Port 80" 2. Using iframe to load the URL and modify its elements via javascript. 3. Using XML Http request and Ajax to make calls. 4. We also tried by JSON mechanism but it needs destination site to support it. We were trying to rewrite URL to look like that belongs to same domain and hopefully this would work. He was able to do some stuff via curl and mod rewrite/mod_proxy, accessing the site's "object", being able to change the text color. But he's stuck recognizing div tags or coloring the images with a different color border because they are being generated dynamically by the site, so stuck at recognizing the elements of the page that are getting. He was trying to read divs and highlight them and he gets a 302 exception, the error you read above. Do you have the experience to help us doing this? Please contact me if you think you can help.
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
PHP, CURL