Re: fetch extension - use local filename from content-disposition header
- From: des@xxxxxx (Dag-Erling Smørgrav)
- Date: Fri, 30 Dec 2005 10:08:12 +0100
Martin Cracauer <cracauer@xxxxxxxx> writes:
> The security implications are about the same as for the base
> functionality. Any filename in the current directory can be wiped
> out if you fetch or wget and a URL redirects to another URL which
> leads to a filename that matches.
No. Fetch uses the original filename as specified on the command
line. Redirects are handled behind the scenes by libfetch.
> The default behavior already *is* that the sending server has control
> over your local naming.
No.
DES
--
Dag-Erling Smørgrav - des@xxxxxx
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- fetch extension - use local filename from content-disposition header
- From: Martin Cracauer
- Re: fetch extension - use local filename from content-disposition header
- From: Barney Wolff
- Re: fetch extension - use local filename from content-disposition header
- From: Sean Bryant
- Re: fetch extension - use local filename from content-disposition header
- From: Pawel Worach
- Re: fetch extension - use local filename from content-disposition header
- From: Martin Cracauer
- fetch extension - use local filename from content-disposition header
- Prev by Date: Re: Help compiling a C utility
- Next by Date: Re: fetch extension - use local filename from content-disposition header
- Previous by thread: Re: fetch extension - use local filename from content-disposition header
- Next by thread: Re: fetch extension - use local filename from content-disposition header
- Index(es):
Relevant Pages
|