You might be able to keep a cache of pages accessed, indexed by the IP of the requester. (If your proxy is on an intranet, this could work. If it's on the Internet, that'll likely screw things up, as IPs can be non-unique due to NAT, firewalls, or other proxies.)

If a request comes in with a relative link, just prepend the last accessed request.

That doesn't seem very robust, and it requires an idealistic situation where you can guarantee that IPs are unique to individual machines. If so, good luck.

Updated: My esteemed colleague spudzeppelin implies one other thing -- with a web-based proxy, you'd have to scan *everything* in the datastream that might possibly be a link, and prepend your URL. That way lies madness.

In reply to Re: Path Fun by chromatic
in thread Path Fun by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.