jenkinsci / jenkinsci/junit-plugin

[JENKINS-21261] CaseResult/index.jelly can be rendered with text/plain content type

Open
#952 7 comments 0 reactions 0 assignees View on GitHub
component:junit-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
87
Forks
351
Avg merge
1d 19h
Merged PRs (30d)
2

Description

CaseResult/index.jelly includes summary.jelly, but a change made by 0460a04f1cafe580d7fd8dff79b28d1cd440346a for JENKINS-19884 makes summary.jelly override the content-type header.

If the servlet container haven't yet committed a response, this will change the effective content type to "text/plain" while some other servlet containers will no doubt render this as "text/html".

I think summary.jelly will send out "text/html" content type, unless I'm missing something. If it really needs to be "text/plain", it should only do so when it's loaded from XmlHttpRequest.

---
Originally reported by kohsuke, imported from: CaseResult/index.jelly can be rendered with text/plain content type


  • status: Open
  • priority: Major
  • component(s): junit-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 3
  • imported: 2025-11-26

Raw content of original issue

CaseResult/index.jelly includes summary.jelly, but a change made by 0460a04f1cafe580d7fd8dff79b28d1cd440346a for JENKINS-19884 makes summary.jelly override the content-type header.

If the servlet container haven't yet committed a response, this will change the effective content type to "text/plain" while some other servlet containers will no doubt render this as "text/html".

I think summary.jelly will send out "text/html" content type, unless I'm missing something. If it really needs to be "text/plain", it should only do so when it's loaded from XmlHttpRequest.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.