Re: fetch extension - use local filename from content-disposition header
- From: Sean Bryant <sean@xxxxxxxxxxxxx>
- Date: Thu, 29 Dec 2005 21:18:07 -0500
Barney Wolff wrote:
On Thu, Dec 29, 2005 at 07:33:38PM -0500, Martin Cracauer wrote:Its just an extra option. I'm sure the details could be summed up in the man page.
I'm a bit rusty, so please point me to style mistakes in the appended
diff.
The following diff implements a "-O" option to fetch(1), which, when
set, will make fetch use a local filename supplied by the server in a
Content-Disposition header.
Have you considered the security implications of this option?
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: fetch extension - use local filename from content-disposition header
- From: Pawel Worach
- Re: fetch extension - use local filename from content-disposition header
- 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
- fetch extension - use local filename from content-disposition header
- Prev by Date: Re: fetch extension - use local filename from content-disposition header
- 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
|
|
