Webflux doesn't close the connection where request heads has "connection: close" [SPR-16309]

[spring-projects-issues]

Alex opened SPR-16309 and commented

Here's a the controller

@GetMapping("/ok")
String ok() {     
    return "ok"; 
}                 

if telneting the server and sending the followed request, the server would send the response headers but not close the connection, while in webmvc it would close.

HEAD /ok HTTP/1.0
Host: 127.0.0.1
Accept: */*
Connection: close

---

Affects: 5.0.2

[spring-projects-issues]

Brian Clozel commented

Hi!
Could you tell us which web server are you using? How are you running your Spring WebFlux application?

[spring-projects-issues]

Alex commented

I'm using spring-boot-starter-webflux:2.0.0.BUILD-SNAPSHOT to build my app, and there no server specified in config file nor included in build file , so i think it would be the default netty.

[spring-projects-issues]

Rossen Stoyanchev commented

We don't have control over the connection at the web framework level, so it sounds like a Reactor Netty issue. For a quick experiment, try adding "spring-boot-starter-tomcat" to see how WebFlux on Tomcat behaves. I suspect it will work as expected since it works on Spring MVC.

[spring-projects-issues]

Brian Clozel commented

Reactor Netty does not support HTTP 1.0, so this might be the underlying issue here.

[spring-projects-issues]

Alex commented

After adding "spring-boot-starter-tomcat" it works as expected. It has good behavior on handling HTTP 1.0 and the Connection header. The link quoted by Brian is very useful. It might be the Reactor Netty's issue. Thx

[spring-projects-issues]

Brian Clozel commented

I'm closing this since this is a Reactor Netty issue.
Thanks for testing Alex!