Yes, I am aware of that. The domain name I wrote "mywebsite" is just a dummy txt that I added to illustrate a point. Sorry I didn't put the correct domain because the website is still under construction.
I get it now. Your original posting was unclear.
My point was that when I follow the link of the broken file path it shows a correct path if I use my original link <src="/images/header.png">
That's an absolute path because of the leading
"/" ("absolute", meaning "from the www root")
"www. yourdomain. com" + "
/images/header.png"
... should end up being "www. yourdomain. com/images/header.png"
If not, check out how the server is setup.
but it shows an incorrect one when I use the absolute path <src="cgi-bin/tkt/images/header.png"> .. in other words this [http://www."mywebsite"/cgi-bin/tkt/images/header.png] exists and should have shown the image but it didn't.
That is
not an absolute path because it does not start with a leading
"/""www. yourdomain. com" +
? + "cgi-bin/tkt/images/header.png"
... will end up being something else depending on which page it was called.
Since the URL was called from this location: "/cgi-bin/tkt/ttx.cgi", then the path will not work at all...
"www. yourdomain. com" + "/cgi-bin/tkt/" + "cgi-bin/tkt/images/header.png"
... and there is your balled up URL.
I'll suggest a basic review of absolute vs. relative URL structure and terminology.