-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble returning pdf docs #27
Comments
Hi @atgreen , I'd like to help, as this is a more than reasonable use case, but I'm kind of disconnected from snooze as of late. Can you supply me with a minimal example, or where to find that
In general yes, this is the current Snooze approach to this. Depending on the backend you've chosen, its practices are likely still viable inside the route's dynamic context, you can probably tell it that the return value is a sequence of octets. For example, in Hunchentoot, you can also do other stuff like setting headers in replies with The adaptation between snooze and the backend you've chosen is probably also a point you can tweak. Just dig around in the code. |
ah nevermind, I missed you were using hunchentoot, my PR is for clack/woo. |
I'm having trouble understanding how to return non-string content. I'm using hunchentoot, and in this case I want to return PDF documents (which are not static content). Do I need to tell the backend not to expect a string result, or is something like this supposed to work?
The text was updated successfully, but these errors were encountered: