Ticket #1 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

HTTP header response for PURLs in error

Reported by: em Assigned to: somebody
Priority: major Milestone: milestone4
Component: component1 Version:
Keywords: Cc:

Description

[cherry 25] ~/ > curl --head http://purlz.org:8100/person/eric 

HTTP/1.1 302 Moved Temporarily
Date: Fri, 02 Nov 2007 18:49:56 GMT
Server: 1060 NetKernel v3.3 - Powered by Jetty
Location: http://zepheira.com/team/eric
X-Purl: 2.0; http://localhost:8080
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: application/void
Content-Length: 0

  • X-Purl setting is incorrect
  • Content-Type is incorrect
  • Expires is incorrect

Change History

03/09/08 03:50:37 changed by em

  • status changed from new to closed.
  • resolution set to fixed.

Resolved in RC4.1

Expires remains the same to minimize caching by applications (which is suggested practice via HTTP spec for 3**, 4** header codes)