Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fragment cache escapes content when using the default parser #1223

Closed
kencarbone opened this issue Apr 5, 2013 · 1 comment
Closed

Fragment cache escapes content when using the default parser #1223

kencarbone opened this issue Apr 5, 2013 · 1 comment
Assignees
@DAddYE
Labels
bug
Milestone
0.11.3

Comments

@kencarbone
Copy link

The fragment cache does not honor the "html safe"-ness of the content it stores when using the default plain-text parser. I think the :marshal parser might be a better default...or perhaps the fragment cache needs to call concat_safe_content rather than concat_content?
@nesquena
Copy link
Member

nesquena commented Apr 8, 2013

@DAddYE thoughts?

@ghost ghost assigned DAddYE Jul 1, 2013
@ujifgc ujifgc closed this as completed in 13fb8e4 Jul 9, 2013
deni64k pushed a commit to deni64k/padrino-framework that referenced this issue Jul 16, 2013
@ujifgc @deni64k
assume value from fragment cache html_safe, fixes padrino#1223
34f7d3d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DAddYE DAddYE

Labels
bug
Projects
None yet
Milestone
0.11.3
Development

No branches or pull requests
3 participants
@nesquena @DAddYE @kencarbone