You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hit a problem when using this piece of middleware along with galetahub-simple_captcha. The captcha gem uses a rack middle ware hook to respond to requests for captcha images written on the fly. With rack-policy in place the headers of these requests were being mangled so that the content length was zero giving a browser error.
I think that the issue lies in that by bypassing response.finish call the body does not get wrapped in a BodyProxy instance and cannot then be safely modified by rack middleware downstream of rack-policy in the middleware chain.
Hope that makes some sort of sense!
Ken
The text was updated successfully, but these errors were encountered:
Hi Ken, thanks for reporting this! Would you mind writing a test for it? For instance, in your test case, you could mock two middlewares that would expose the problem! Also if you could provide me with sample code that you are using to replicate the bug?
I hit a problem when using this piece of middleware along with galetahub-simple_captcha. The captcha gem uses a rack middle ware hook to respond to requests for captcha images written on the fly. With rack-policy in place the headers of these requests were being mangled so that the content length was zero giving a browser error.
I think that the issue lies in that by bypassing response.finish call the body does not get wrapped in a BodyProxy instance and cannot then be safely modified by rack middleware downstream of rack-policy in the middleware chain.
Hope that makes some sort of sense!
Ken
The text was updated successfully, but these errors were encountered: