Links Anomoly - HELP

  • Thread starter Thread starter Goober
  • Start date Start date
G

Goober

Help,

I am creating some webpages for someone (B) who uses FrontPage 98 (I
do not use FrontPage but create html files with wordpad).

PROBLEM:

I post a new page to my server. B downloads it. But when he posts that
new page to his server, the links on it are all directed to my server
even though the links on the page I created did not have any
information about my server or URL.

Assuming B’s FrontPage program is automatically editing the file based
on the location he downloaded it from, I emailed the same file as an
attachment, again with no information about my server in it. This way
FrontPage should not associate the emailed file with my site. He posts
the new emailed file, yet lo and behold, the links once again become
directed to my site as if by magic!

What’s up? How to stop this from happening?

From his POV, I’m giving him a page that has links to my site. From my
POV, I know and can see that the html files I’m creating and sending
have NO data about my server or URL.

Thanks!
 
my guess is your friend is doing something wrong on his end, or there is an
html version of the htm file you sent him. I can't see how server
extensions or his client program could do this. I think he's screwing it up
locally and posting the result.
this is all just an assumption but you might want to find out exactly what
and how he's doing it.
IMHO
 
How is B downloading the file?
If B is viewing the file in Internet Explorer and then using File-SaveAs to
save the file, the links *will* be changed to point to your website (and
some extra meta tags are added to the page, as well). The Save As dialogue
also gives B the opportunity to change the file name and extension, since IE
will suggest "Page Title.htm" (including spaces) as the saved filename.
To cure this B should View Source, then save the source as a new filename,
this does not change any of the HTML, but again B has to create the filename
and extension.
The emailed version would probably have been saved with *your* choice of
filename.extn - hence the possibility of two different files and the wrong
one processed in FP.

HTH
Ron
 
Back
Top