Re: fetch extension - use local filename from content-disposition header
- From: Barney Wolff <barney@xxxxxxxxxxx>
- Date: Thu, 29 Dec 2005 21:16:02 -0500
On Thu, Dec 29, 2005 at 07:33:38PM -0500, Martin Cracauer wrote:
> 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?
--
Barney Wolff http://www.databus.com/bwresume.pdf
I never met a computer I didn't like.
_______________________________________________
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: Sean Bryant
- Re: fetch extension - use local filename from content-disposition header
- References:
- fetch extension - use local filename from content-disposition header
- From: Martin Cracauer
- fetch extension - use local filename from content-disposition header
- Prev by Date: 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: 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
|
|
