Forum Discussion
RFC2616 - content-disposition with special characters - Problem to export file
Hello
The cause of the problem, is like the SOL said, a back end answer that not compliance with the RCF.
We are analyzing the tcpdump captures and httpwatch.
Until this moment we identify one beahvior. content-disposition there is special characteres like example:
content-disposition= attachement;filename=FILE_teste_01/01/2001 10:08:01.xlsx;size=196...
Probably these special characters in content that is not compliant with RFC2616.
if that behavior can not be corrected the application side, can I solve that with some irule? irule Replace content can resolve? If someone can quote some example that would answer
thank you very much
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com