Dear all,
First I'd like to thank all devs for your great work in naviserver.
I had been using aolserver 4.5 for one legacy project for a very long
time. A couple of years ago I replaced it for naviserver and has been
very happy for the great improvement in stability and
performance since then.
Dear Gustaf,
Thank you very much for your help.
It does work perfectly, therefore it is configuration related.
I'll work with my setup and double check everything in the config
file.
When I pinpoint the problem I'll post the solution to close the
thread.
Best regards,
Óscar
-Mensaje origi
Dear all,
Just for the sake of completeness. If you need an utf-8 encoded
filename you may need to encode the filename (as per RFC 5987):
ns_set update [ns_conn outputheaders] Content-Disposition
"attachment; filename*=UTF-8''[ns_urlencode $filename]"
ns_set update [ns_conn outputheaders] Conten
hould actually provide an API along the lines of:
ns_header_field_parameter -charset /charset/ -language /language/
name string
to ease its usage. ... maybe something for the next release...
All the best
-g
PS: Minor nitpick: RFC 5987 was obsoleted by RFC 8187
On 19.07.22 23:25, Oscar Rodriguez Fo
