I will explain a little more detail so it makes sense. I almost need a "plug-in" or to build something that will either rewrite the hard-coded IP's in the returned HTML file, or allow a substitution of the hard-coded IP with the REAL IP when clicking. Let me explain more....
Website I am accessing is let's say for example, 10.20.40.80
I go to
http://10.20.40.80/images.html in my browser. OK. So it returns a web page, whose content for example is this:
<html>
<body>
Thumbnails:
<img src="http://0.0.0.0/image1.jpg">
<img src="http://0.0.0.0/image2.jpg">
<img src="http://0.0.0.0/image3.jpg">
</body>
</html>
Obviously the browser shows no images because the IP hard-coded in the returned HTML file is wrong. In this case it is 0.0.0.0. In other cases, the IP may be 55.1.0.0. Whatever the case may be, it is CONSISTENT but WRONG.
NOTE: I did NOT write those HTML pages. They are automatically generated by the hard-drive software, and just reveal content in various folders on the drive. The problem is the software erroneously (or maybe on purpose) uses the wrong IP when it returns the HTML file listing the files. It doesn't actually put in the publicly-listed IP. So even though you can query the hard drive and get an HTML page back from outside (on the public internet), it is using some strange IP from I don't know where on the page. This could be 0.0.0.0, it could be 10.0.0.10, it could even sometimes be 192.168.1.1 or similar. But *NOT* the public IP.
I need that HTML file that is returned from the server at 10.20.40.80 to look like this:
<html>
<body>
Thumbnails:
<img src="http://10.20.40.80/image1.jpg">
<img src="http://10.20.40.80/image2.jpg">
<img src="http://10.20.40.80/image3.jpg">
</body>
</html>
So in the second case, the hard-coded IP is correct and images are properly loaded. OK. So what I am doing now is SAVING the first HTML file returned (with 0.0.0.0 hard-coded in it) and doing a "sed" replace operation which takes 0.0.0.0 --> 10.20.40.80. The resultant HTML file (the 2nd example above) will properly load the images from the server at 10.20.40.80.
OPTION 1:If there is some kind of "filter" or "plug-in" which will pattern-match to the "0.0.0.0" (or whatever the wrong IP happens to be) prior to the page loading, or doing a replacement substitution WITHIN the browser itself, that could work. In that case, all instances of "0.0.0.0" in the page will end up turning into "10.20.40.80" and the page will reference the correct server directories.
OPTION 2:If I can do an IP-routing subtitution say for OUTBOUND requests, that turns a request for "0.0.0.0" to instead query the IP 10.20.40.80, then even though the hard-coded HTML page that is loaded contains references to "0.0.0.0" everywhere, my LINUX system would actually be going to 10.20.40.80 (instead of 0.0.0.0) to grab the file.... Since the file is at 10.20.40.80 and NOT at 0.0.0.0.
Otherwise, as I mentioned, I have to SAVE each HTML file I get back, run a "sed" on it to replace all IP's, then reload in browser... which in theory I could automate but it is annoying and wastes time.