ldp.html
changeset 937 ae4acedaf21b
parent 935 4c9e4a9dc2e8
child 938 859f98c26867
equal deleted inserted replaced
936:391bf26afb13 937:ae4acedaf21b
  2469 <p>As with any protocol that is implemented leveraging HTTP, implementations should take advantage of the many 
  2469 <p>As with any protocol that is implemented leveraging HTTP, implementations should take advantage of the many 
  2470 security-related facilities associated with it and are not required to carry out LDP operations 
  2470 security-related facilities associated with it and are not required to carry out LDP operations 
  2471 that may be in contradistinction to a particular security policy in place. For example, when faced with an 
  2471 that may be in contradistinction to a particular security policy in place. For example, when faced with an 
  2472 unauthenticated request to replace system critical RDF statements in a graph through the PUT method, applications may
  2472 unauthenticated request to replace system critical RDF statements in a graph through the PUT method, applications may
  2473 consider responding with the 401 status code (Unauthorized), indicating that the appropriate authorization 
  2473 consider responding with the 401 status code (Unauthorized), indicating that the appropriate authorization 
  2474 is required. In cases where authentication is provided fails to meet the requirements of a particular access control 
  2474 is required. In cases where the provided authentication fails to meet the requirements of a particular access control 
  2475 policy, the 403 status code (Forbidden) can be sent back to the client to indicate this failure to meet the
  2475 policy, the 403 status code (Forbidden) can be sent back to the client to indicate this failure to meet the
  2476 access control policy.</p>
  2476 access control policy.</p>
  2477 </section>
  2477 </section>
  2478 
  2478 
  2479 <section class='appendix informative'>
  2479 <section class='appendix informative'>
  2524 <!-- 
  2524 <!-- 
  2525 <h2>Detailed history</h2> -->
  2525 <h2>Detailed history</h2> -->
  2526 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/PR-ldp-20141216/">Proposed Recommendation Draft</a></em></blockquote> -->
  2526 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/PR-ldp-20141216/">Proposed Recommendation Draft</a></em></blockquote> -->
  2527 <!-- 
  2527 <!-- 
  2528 <ul>
  2528 <ul>
       
  2529 	<li>2015-01-26 - AC rep comment #1 on clarity in security considerations (SS)</li>
  2529 	<li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li>
  2530 	<li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li>
  2530 </ul>
  2531 </ul>
  2531 -->
  2532 -->
  2532 
  2533 
  2533 <!-- 
  2534 <!--