[Archive-access-discuss] FTP URL in base dir

[Thakur, P. <Pra...@on...>]

Hi everyone,

I was wondering if an ftp url can be in wayback.xml?
I am having issues with it. I am on windows XP.

The error is C:\Program Files\Apache Software Foundation\Tomcat 6.0\ftp:\user:pass@188.44.99.300\repository\waybacktest\election2011Test is not a directory

My configuration is wayback.xml is
wayback.basedir=ftp://user:pass@188.44.99.300/repository/waybacktest


Can someone please give me some ideas?

Thanks,

--Pramila Thakur
________________________________
From: Bradley Tofel [mailto:br...@ar...]
Sent: Tuesday, June 07, 2011 4:08 PM
To: arc...@li...
Subject: Re: [Archive-access-discuss] Absolute path and relative path solution

Hi Pramila,

I didn't yet have a chance to respond to your previous post about javascript menus. Is this the situation you're facing?

Can you provide some example URLs, or HTML + JS snippets to help clarify the situation?

Some background - there are 3 types of URLs:

1) absolute (ex, "http://www.example.org/images/foo.gif"<http://www.example.org/images/foo.gif>)
2) server relative (ex, "/images/foo.gif")
3) path relative (ex, "../images/foo.gif", "images/foo.gif")

Wayback attempts to rewrite all URLs found in HTML. It attempts to rewrite absolute URLs found in javascript and CSS.

This leaves server-relative and path-relative URLs.

Path relative URLs should require no rewriting (unless they include ../../../../ references which back up beyond the actual server root...):

Page: http://wayback.example.com/20010101000000/http://www.example.org/<http://wayback.example.com/20010101000000/http:/www.example.org/>
Containing: "images/foo.gif"
Resolves to "http://wayback.example.com/20010101000000/http://www.example.org/images/foo.gif"<http://wayback.example.com/20010101000000/http:/www.example.org/images/foo.gif>

which is correct.

Server-relative links do not go to the right place:
Page: http://wayback.example.com/20010101000000/http://www.example.org/<http://wayback.example.com/20010101000000/http:/www.example.org/>
Containing: "/images/foo.gif"
Resolves to "http://wayback.example.com/images/foo.gif"<http://wayback.example.com/images/foo.gif>

which is *not* correct.

Wayback does include a server-relative redirection handler. This notices incoming URLs like:

"/images/foo.gif"

and uses the "Referer" HTTP request header to correctly resolve the URL, redirecting the request back to the correct:

"http://wayback.example.com/20010101000000/http://www.example.org/images/foo.gif"<http://wayback.example.com/20010101000000/http:/www.example.org/images/foo.gif>

Note that this requires some specific configuration choices, most importantly, Wayback must be deployed at the ROOT context.

Unless Wayback is run at the ROOT context, it will not have an opportunity to handle the stray server-relative requests to bounce them back on track.

I'm guessing this is the issue you're seeing, but I might be misinterpreting your question.

Brad

On 6/7/11 12:09 PM, Pra...@on...<mailto:Pra...@on...> wrote:
Hi Everyone,

I am facing an issue with links that have absolute and relative URL's in their href.

If a site has absolute path in the links, then wayback is replaying it fine.
But if the links have the URL's that are relative to the document, then wayback does not seem to replay it correctly.

Has anyone faced the same situation?
Is there a workaround for this to replay it correctly in wayback?

Thanks,

--Pramila





------------------------------------------------------------------------------

EditLive Enterprise is the world's most technically advanced content

authoring tool. Experience the power of Track Changes, Inline Image

Editing and ensure content is compliant with Accessibility Checking.

http://p.sf.net/sfu/ephox-dev2dev





_______________________________________________

Archive-access-discuss mailing list

Arc...@li...<mailto:Arc...@li...>

https://lists.sourceforge.net/lists/listinfo/archive-access-discuss