Ticket #116 (closed Enhancement: Out of scope)

Opened 3 years ago

Last modified 18 months ago

Content-Type in response even if Content-Length=0 ?

Reported by: ibc Owned by: adigeo
Priority: Minor Milestone: Nice to have
Component: Interoperability Version: trunk
Severity: Non-critical Keywords:
Cc:

Description

After a succesful PUT action OpenXCAP replies: 

HTTP/1.1 200 OK
Date: Wed, 15 Jul 2009 16:54:29 GMT
Content-Length: 0
ETag: "6bcf3690929ca4f24d697838e9af1242"
Content-Type: application/auth-policy+xml
Server: OpenXCAP/1.1.0
Connection: close

Since Content-Length is 0, does Content-Type header make sense?

Change History

comment:1 Changed 2 years ago by adigeo

  • Owner changed from support@ag-projects.com to adigeo
  • Status changed from new to accepted

Indeed this is not very elegant. But does it hurt a client, any experience related to this?

comment:2 Changed 2 years ago by ibc

I've seen no problem with HTTP clients (I've tested no so many however) but IMHO a response to a PUT request shouldn't contain a Content-Type matching the PUT Content-type as it makes no sense.

comment:3 Changed 2 years ago by adigeo

  • Version changed from 1.1.0 to trunk
  • Type changed from Defect to Enhancement

comment:4 Changed 18 months ago by adigeo

  • Status changed from accepted to closed
  • Resolution set to Out of scope
Note: See TracTickets for help on using tickets.