wget-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Wget-dev] wget2 | Dealing with 301 Redirects and Recursion (#383)


From: Darshit Shah
Subject: [Wget-dev] wget2 | Dealing with 301 Redirects and Recursion (#383)
Date: Sun, 27 May 2018 09:42:34 +0000

New Issue was created.

Issue 383: https://gitlab.com/gnuwget/wget2/issues/383
Author:    Darshit Shah
Assignee:  

So, I came across an interesting scenario earlier today. I was trying to 
recursively download a website with `--no-parent -r`.

The website is hosted using `nginx` and uses the `auto_index` module. Which 
means a request for `/foo/` will automatically generate an index file and serve 
it.
The exact command I used was `wget2 --no-parent -r example.com/foo/bar` where 
`bar` is a directory. So, as expected, the server responds with a `301 
Permanently Moved` to `/foo/bar/` and then proceeds to serve an index file.

However, since `wget2` doesn't accept the new server name for the download, the 
iri still contains `/foo/bar` as the location. This means all files in `/foo/` 
are also considered as part of the current directory even though they really 
are a part of the parent.

Now, this can be easily dealt with if we simply consider the IRI to the new 
one. But it may cause interesting side-effects. So I want to discuss this here 
before making any changes

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnuwget/wget2/issues/383
You're receiving this email because of your account on gitlab.com.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]