----- "Mark Montague" <m...@catseye.org> wrote:
> On January 4, 2011 22:32 , Carlos S <neu...@gmail.com> wrote:
> > Recently I was trying to download a package using wget, but the
> > website prevented access to it. I tried --user-agent option but it
> > didn't work either. So I was curious to know what strategy this web
> > admin must have implemented.
>
> Without an example URL, I can only speculate, but the ideas that come
> to
> mind first are denying the download unless a cookie is set (you could
i.ga...@panic ~ % wget --help | grep cook
--no-cookies don’t use cookies.
--load-cookies=FILE load cookies from FILE before session.
--save-cookies=FILE save cookies to FILE after session.
--keep-session-cookies load and save session (non-permanent) cookies.
i.ga...@panic ~ %
> get quite complex with this, such as setting the cookie via
> JavaScript,
Yup.. that (JS) would kill off wget.. but also many other (sensible) clients
> which wget won't execute), checking the referrer header, or other
i.ga...@panic ~ % wget --help | grep -i referer
--referer=URL include ‘Referer: URL’ header in HTTP request.
i.ga...@panic ~ %
> JavaScript based checks.
i
> --
> Mark Montague
> m...@catseye.org
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
