Html Response getting downloaded instead of displaying with content-type : application/octet-stream in wildfly server [SPR-12558]

[spring-projects-issues]

sreekanth opened SPR-12558 and commented

I was waiting for a reply since 2 working days for the below stackoverflow post, didn get any solution yet. Since i'm suspecting it as a bug and in an urgency to bring spring-mvc.

http://stackoverflow.com/questions/27547448/spring-mvc-latest-html-response-is-getting-downloaded-instead-of-displaying

My request url is http://localhost:port/sample/common/hello and i'm expecting a html output but its turns out application/octet-stream and downloading my html content of jsp.

I suspect it as a bug, if not Is there anything i'm missing in my spring config ?

Attaching war as well as source code

---

Affects: 4.1.3

Attachments:

• sample.tar.gz (8.76 MB)
• sample-new.tar.gz (6.53 kB)

Referenced from: commits spring-attic/spring-framework-issues@b8f3df9, spring-attic/spring-framework-issues@a0f67fc

[spring-projects-issues]

sreekanth commented

Hi Brian,
I have updated the curl header out put and the log in stackoverflow, can you please have a look on it. Are you able to reproduce the problem with the war i have attached ?

[spring-projects-issues]

sreekanth commented

As an update if i dont use WebApplicationInitializer and instead if i use web.xml with the following minimum content

<context-param>
		<param-name>contextClass</param-name>
		<param-value>
			org.springframework.web.context.support.AnnotationConfigWebApplicationContext
		</param-value>
	</context-param>
	<listener>
		<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
	</listener>

	<servlet>
		<servlet-name>SpringDispatcher</servlet-name>
		<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
		<init-param>
			<param-name>contextClass</param-name>
			<param-value>
				org.springframework.web.context.support.AnnotationConfigWebApplicationContext
			</param-value>
		</init-param>
		<init-param>
			<param-name>contextConfigLocation</param-name>
			<param-value>org.egov</param-value>
		</init-param>
		<load-on-startup>1</load-on-startup>
	</servlet>
	<servlet-mapping>
		<servlet-name>SpringDispatcher</servlet-name>
		<url-pattern>/</url-pattern>
	</servlet-mapping>

[spring-projects-issues]

Rossen Stoyanchev commented

Why do you think this is a Spring MVC bug? Have you tried running on another container? Or tried a simple JSP rendering app?

[spring-projects-issues]

sreekanth commented

No I didnt try running in another container. I'm pretty much unsure about whose problem it is, even i'm suspecting Wildfly as well and already asked in their community.

[spring-projects-issues]

sreekanth commented

As an update on this issue, i have used normal ServletContainerInitializer implementation to load and wire up spring (without web.xml), that's working perfectly as well..

Hi Rossen,
I guess this will clarify why i doubt it can either be spring mvc issue.

Please check the attached war project sample-new.tar.gz.

[spring-projects-issues]

Sébastien Deleuze commented

Hi sreekanth, I have used the project you attached to create this spring-framework-issues repro project and was not able to reproduce the issue you described with Wildfly 8.2.0.Final. The http://localhost:port/sample/common/hello page is displayed as expected in the browser with a text/html content type.

Could you detail how to reproduce it based on this project ?

[spring-projects-issues]

sreekanth commented

Hi Sebastien,
Yeah your github version will work, because its having web.xml. You can reproduce the issue with my first attachment https://jira.spring.io/secure/attachment/22439/sample.tar.gz where web.xml is not present and having only AbstractAnnotationConfigDispatcherServletInitializer implementation. You may reproduce from your github project by removing web.xml and adding javaconfig.

My second attachment https://jira.spring.io/secure/attachment/22441/sample-new.tar.gz which doesn't have web.xml but here i'm not using AbstractAnnotationConfigDispatcherServletInitializer but with my custom ServletContainerInitializer implementation wiring spring stuffs up.

[spring-projects-issues]

Sébastien Deleuze commented

I have updated the repro project in order to use the ServletInitializer instead of web.xml, and I could reproduce the issue, but I think the behavior you observe come from a mistake in your WebAppInitializer.java class:

protected String[] getServletMappings() {
     return new String[] { "/*" };
}

It can be fixed with:

protected String[] getServletMappings() {
     return new String[] { "/" };
}

Could you confirm it fixes the issue ?

[spring-projects-issues]

sreekanth commented

Thanks Sébastien, that resolves the issue but there was two issue which haunted me so long.

I have observed this pattern issue at the beginning itself and checked by changing from /* to / and / to /* but had no luck. The funny part was, i was checking in chrome browser.

First issue was in Wildfly the url pattern should be / instead of /*.
The second issue was chrome browser cache (that was the main evil drag me till here)

When I posted curl header output in stackoverflow, i was using /* url mapping, thats the reason curl shown application/octet-stream.

I'm extremely sorry for filing this as an issue, you can close this issue.

Thanks you for your prompt support to find the hidden evil :) .

[spring-projects-issues]

Sébastien Deleuze commented

Your're welcome, thanks for your quick feedback.