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
tsteur opened this issue
Sep 18, 2014
· 3 comments
Labels
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Getting the error "error on line 4 at column 8: Opening and ending tag mismatch: meta line 0 and head". When fixing the not closed meta tag I am getting the next error "error on line 52 at column 27: Entity 'nbsp' not defined".
header should be text/html probably.
One should be able to reproduce it when clicking in scheduled reports on "download" or "send report now". Format should be HTML
The text was updated successfully, but these errors were encountered:
…he link to download.
The issue is that this data returned by the method is going through the Api Renderer which then sets the content type header. Instead we should skip the API renderer somehow for these API methods that return data and set their own headers?
I'm closing after 60792cb which should fix it, though it's a workaround and there instead should be a way for data not to go through the ResponseBuilder that sends content type headers. (format=original didn't work as it set text/plain content type for added protection against xss)
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Problem is it sends the header text/xml.
Getting the error "error on line 4 at column 8: Opening and ending tag mismatch: meta line 0 and head". When fixing the not closed meta tag I am getting the next error "error on line 52 at column 27: Entity 'nbsp' not defined".
header should be text/html probably.
One should be able to reproduce it when clicking in scheduled reports on "download" or "send report now". Format should be HTML
The text was updated successfully, but these errors were encountered: