fix incorrect partial content response to HEAD request with-Range-header, or from Not-accept-range server

[Chenjp]

• Bug: incorrect partial content response to HEAD request with-Range-header
  Tomcat - 206:

    C:\Users\chenjp>curl http://localhost:55263/index.html -i -H "Range: bytes=0-10" -I
    HTTP/1.1 206
    vary: accept-encoding
    Accept-Ranges: bytes
  

  www.apache.org offcial site - 200:

  C:\Users\chenjp>curl https://www.apache.org -i -H "Range: bytes=0-10" -I
  HTTP/1.1 200 OK
  Connection: keep-alive
  Content-Length: 64483
  

• Bug: receives a partial content sc from a Not-accept-range server

  C:\Users\chenjp>curl http://localhost:55463/index.html -i -H "Range: bytes=0-10"
  HTTP/1.1 206
  vary: accept-encoding
  ETag: W/"957-1732881015126"
  

ChangeLog:

• per RFC 9110 - Section 14, currently GET is the only method.
• A server that turn off accept-range support should ignore Range header field.