draft-laugstol-apache-maven-repository-rest-applications-05.txt		draft-laugstol-apache-maven-repository-rest-applications-06.txt
	skipping to change at page 2, line 9		skipping to change at page 2, line 9
	3.4.2. Download a set of artifacts . . . . . . . . . . . . . 5		3.4.2. Download a set of artifacts . . . . . . . . . . . . . 5
	3.5. Searching . . . . . . . . . . . . . . . . . . . . . . . . 5		3.5. Searching . . . . . . . . . . . . . . . . . . . . . . . . 5
	3.6. List Repositories . . . . . . . . . . . . . . . . . . . . 6		3.6. List Repositories . . . . . . . . . . . . . . . . . . . . 6
	4. Security Aspects . . . . . . . . . . . . . . . . . . . . . . . 6		4. Security Aspects . . . . . . . . . . . . . . . . . . . . . . . 6
	4.1. Authentication and Authorization . . . . . . . . . . . . . 6		4.1. Authentication and Authorization . . . . . . . . . . . . . 6
	5. User-Agent Considerations . . . . . . . . . . . . . . . . . . 6		5. User-Agent Considerations . . . . . . . . . . . . . . . . . . 6
	5.1. Caching . . . . . . . . . . . . . . . . . . . . . . . . . 6		5.1. Caching . . . . . . . . . . . . . . . . . . . . . . . . . 6
	5.2. Multiple links . . . . . . . . . . . . . . . . . . . . . . 6		5.2. Multiple links . . . . . . . . . . . . . . . . . . . . . . 6
	5.3. Forms . . . . . . . . . . . . . . . . . . . . . . . . . . 6		5.3. Forms . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	5.4. Server Responses . . . . . . . . . . . . . . . . . . . . . 6		5.4. Server Responses . . . . . . . . . . . . . . . . . . . . . 7
	5.4.1. Single Artifact . . . . . . . . . . . . . . . . . . . 6		5.4.1. Single Artifact . . . . . . . . . . . . . . . . . . . 7
	5.4.2. Multiple Artifacts . . . . . . . . . . . . . . . . . . 6		5.4.2. Multiple Artifacts . . . . . . . . . . . . . . . . . . 7
	5.4.2.1. text/uri-list . . . . . . . . . . . . . . . . . . 7		5.4.2.1. text/uri-list . . . . . . . . . . . . . . . . . . 7
	5.5. HTTP Binding . . . . . . . . . . . . . . . . . . . . . . . 7		5.5. HTTP Binding . . . . . . . . . . . . . . . . . . . . . . . 7
	6. Appendix: Words and Definitions . . . . . . . . . . . . . . . 7		6. Appendix: Words and Definitions . . . . . . . . . . . . . . . 7
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 7		7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	8.1. Link Relation: http://maven.apache.org/rel/pom . . . . . . 8		8.1. Link Relation: http://maven.apache.org/rel/pom . . . . . . 8
	8.2. Link Relation: http://maven.apache.org/rel/md5 . . . . . . 8		8.2. Link Relation: http://maven.apache.org/rel/md5 . . . . . . 8
	8.3. Link Relation: http://maven.apache.org/rel/sha1 . . . . . 8		8.3. Link Relation: http://maven.apache.org/rel/sha1 . . . . . 8
	8.4. Media Type: text/vnd.maven.pom . . . . . . . . . . . . . . 8		8.4. Media Type: text/vnd.maven.pom . . . . . . . . . . . . . . 8
	8.5. Media Type: text/vnd.maven.md5 . . . . . . . . . . . . . . 8		8.5. Media Type: text/vnd.maven.md5 . . . . . . . . . . . . . . 8
	8.6. Media Type: text/vnd.maven.sha1 . . . . . . . . . . . . . 8		8.6. Media Type: text/vnd.maven.sha1 . . . . . . . . . . . . . 8
	8.7. URN Registration: urn:maven:artifact . . . . . . . . . . . 8		8.7. URN Registration: urn:maven:artifact . . . . . . . . . . . 8
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 8		9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8		10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8		11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	skipping to change at page 6, line 30		skipping to change at page 6, line 31
	when requesting artifacts. This make it possible for caches to		when requesting artifacts. This make it possible for caches to
	include caching information in the return response that intermediates		include caching information in the return response that intermediates
	also will use.		also will use.
	TODO: Are there any standard ways in HTTP to do this?		TODO: Are there any standard ways in HTTP to do this?
	A user agent must always check that it got the data it required after		A user agent must always check that it got the data it required after
	receiving a response. This means checking response code and content		receiving a response. This means checking response code and content
	type in particular.		type in particular.
			User agents should implement a way to force an updated answer from
			the server, similar to what contemporary web browser to when the user
			explicitly reloads a page. For HTTP this includes sending a "max-
			age=0" when requesting the data. This spesification specifically
			allows servers to send "410 Gone" (See HTTP/1.1, Section 10.4.11) for
			artifacts that it knows won't ever come. A case where this is useful
			is if an artifact is uploaded and it's sources and javadoc artifacts
			are not there. A user agent MUST use any caching info given with the
			response. By specification the response can be cached forever.
			TODO: Add info on "305 Use Proxy", section 10.3.6 of HTTP/1.1.
	5.2. Multiple links		5.2. Multiple links
	If a response include many links with the same relation and content		If a response include many links with the same relation and content
	type, it should can try all links to get the data. This makes it		type, it should can try all links to get the data. This makes it
	possible for a server to include pointers to many servers that can		possible for a server to include pointers to many servers that can
	respond to the same request. A user agent should try to stick to the		respond to the same request. A user agent should try to stick to the
	same host (as defined by the URI) for the following requests.		same host (as defined by the URI) for the following requests.
	TODO: It this mainly covered by metalink?		TODO: It this mainly covered by metalink?
End of changes. 3 change blocks.
	5 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/