bug-wget
[Top][All Lists]
Advanced

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

[Bug-wget] [bug #53322] Add option to let page-requisites bypass no-pare


From: David
Subject: [Bug-wget] [bug #53322] Add option to let page-requisites bypass no-parent
Date: Sun, 11 Mar 2018 07:43:27 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?53322>

                 Summary: Add option to let page-requisites bypass no-parent
                 Project: GNU Wget
            Submitted by: mcdado
            Submitted on: Sun 11 Mar 2018 11:43:25 AM UTC
                Category: Feature Request
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
        Operating System: None
         Reproducibility: Every Time
           Fixed Release: None
         Planned Release: None
              Regression: None
           Work Required: None
          Patch Included: None

    _______________________________________________________

Details:

When using `--no-parent` and `--page-requisites`, if the page requires images
or other requisites from that domain but higher in hierarchy, it will not
proceed to download those requisites because of the `no-parent` option. While
`no-parent` is useful for web pages (without it you download a whole site,
especially if you `--mirror`) so it would be good to have an extra option to
allow downloading page requisites that are higher in the hierarchy.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53322>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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