Documentation Falcon Documentation, Release 3.1.1b3 Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content- Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 recommendations, non-ASCII filenames

Documentation Falcon Documentation, Release 3.1.1b1 Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content- Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 recommendations, non-ASCII filenames

5. Documentation Falcon Documentation, Release 3.1.1 Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content- Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 recommendations, non-ASCII filenames

5. Documentation Falcon Documentation, Release 3.1.0 Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content- Disposition header would be set to: 'attachment; filename="report.pdf"'. 5.4. Framework Reference 143 Falcon Documentation,

5. Documentation Falcon Documentation, Release 3.1.1 Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content- Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 recommendations, non-ASCII filenames

Documentation Falcon Documentation, Release 3.1.1rc1 Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content- Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 recommendations, non-ASCII filenames

Content-Type header set to multipart/form- data; boundary=AaB03x. Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content-Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 [https://tools.ietf.org/html/rfc6266#appendix-D]

Content-Type header set to multipart/form- data; boundary=AaB03x. Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content-Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 [https://tools.ietf.org/html/rfc6266#appendix-D]

Content-Type header set to multipart/form- data; boundary=AaB03x. Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content-Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 [https://tools.ietf.org/html/rfc6266#appendix-D]

Content-Type header set to multipart/form- data; boundary=AaB03x. Outputting CSV Files Generating a CSV (or PDF, etc.) report and making it available as a downloadable file is a fairly common back-end service task header. Falcon includes the downloadable_as property to make this easy: resp.downloadable_as = 'report.pdf' See also the Outputting CSV Files recipe for a more involved example of dynamically generated downloadable used for the filename directive. For example, given 'report.pdf', the Content-Disposition header would be set to: 'attachment; filename="report.pdf"'. As per RFC 6266 [https://tools.ietf.org/html/rfc6266#appendix-D]