2 # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
4 # Copyright 2013-2014 Oracle and/or its affiliates. All rights reserved.
6 # Oracle and Java are registered trademarks of Oracle and/or its affiliates.
7 # Other names may be trademarks of their respective owners.
9 # The contents of this file are subject to the terms of either the GNU
10 # General Public License Version 2 only ("GPL") or the Common
11 # Development and Distribution License("CDDL") (collectively, the
12 # "License"). You may not use this file except in compliance with the
13 # License. You can obtain a copy of the License at
14 # http://www.netbeans.org/cddl-gplv2.html
15 # or nbbuild/licenses/CDDL-GPL-2-CP. See the License for the
16 # specific language governing permissions and limitations under the
17 # License. When distributing the software, include this License Header
18 # Notice in each file and include the License file at
19 # nbbuild/licenses/CDDL-GPL-2-CP. Oracle designates this
20 # particular file as subject to the "Classpath" exception as provided
21 # by Oracle in the GPL Version 2 section of the License file that
22 # accompanied this code. If applicable, add the following below the
23 # License Header, with the fields enclosed by brackets [] replaced by
24 # your own identifying information:
25 # "Portions Copyrighted [year] [name of copyright owner]"
29 # The Original Software is NetBeans. The Initial Developer of the Original
30 # Software is Oracle. Portions Copyright 2013-2014 Oracle. All Rights Reserved.
32 # If you wish your version of this file to be governed by only the CDDL
33 # or only the GPL Version 2, indicate your decision by adding
34 # "[Contributor] elects to include this software in this distribution
35 # under the [CDDL or GPL Version 2] license." If you do not indicate a
36 # single choice of license, a recipient has the option to distribute
37 # your version of this file under either the CDDL, the GPL Version 2 or
38 # to extend the choice of license to its licensees as provided above.
39 # However, if you add GPL Version 2 code and therefore, elected the GPL
40 # Version 2 license, then the option applies only if the new code is
41 # made subject to such option by the copyright holder.
44 MSG_Completion_GET=The GET method means retrieve whatever information \
45 (in the form of an entity) is identified by the Request-URI. \
46 If the Request-URI refers to a data-producing process, \
47 it is the produced data which shall be returned as the entity in \
48 the response and not the source text of the process, \
49 unless that text happens to be the output of the process.
51 MSG_Completion_HEAD=The HEAD method is identical to GET except that the server \
52 MUST NOT return a message-body in the response. The metainformation \
53 contained in the HTTP headers in response to a HEAD request SHOULD be \
54 identical to the information sent in response to a GET request. \
55 This method can be used for obtaining metainformation about the entity implied \
56 by the request without transferring the entity-body itself. \
57 This method is often used for testing hypertext links for validity, \
58 accessibility, and recent modification.
60 MSG_Completion_POST=The POST method is used to request that the origin server \
61 accept the entity enclosed in the request as a new subordinate of the resource \
62 identified by the Request-URI in the Request-Line. POST is designed to allow \
63 a uniform method to cover annotation of existing resources,\
64 posting a message to a bulletin board, newsgroup, mailing list, or similar \
65 group of articles, providing a block of data, such as the result of submitting a \
66 form, to a data-handling process or extending a database through an append operation. \
67 The actual function performed by the POST method is determined by the server \
68 and is usually dependent on the Request-URI. The posted entity is subordinate \
69 to that URI in the same way that a file is subordinate to a directory containing it, \
70 a news article is subordinate to a newsgroup to which it is posted, \
71 or a record is subordinate to a database.
73 MSG_Completion_PUT=The PUT method requests that the enclosed entity be stored \
74 under the supplied Request-URI. If the Request-URI refers to an already \
75 existing resource, the enclosed entity SHOULD be considered as a modified \
76 version of the one residing on the origin server. If the Request-URI does \
77 not point to an existing resource, and that URI is capable of being defined \
78 as a new resource by the requesting user agent, the origin server can \
79 create the resource with that URI. If a new resource is created, the origin \
80 server MUST inform the user agent via the 201 (Created) response. \
81 If an existing resource is modified, either the 200 (OK) or 204 (No Content) \
82 response codes SHOULD be sent to indicate successful completion of the request. \
83 If the resource could not be created or modified with the Request-URI, an \
84 appropriate error response SHOULD be given that reflects the nature of the problem. \
85 The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) \
86 headers that it does not understand or implement and MUST return \
87 a 501 (Not Implemented) response in such cases.
89 MSG_Completion_DELETE=The DELETE method requests that the origin server delete \
90 the resource identified by the Request-URI. This method MAY be overridden \
91 by human intervention (or other means) on the origin server. The client \
92 cannot be guaranteed that the operation has been carried out, even if \
93 the status code returned from the origin server indicates that the action \
94 has been completed successfully. However, the server SHOULD NOT indicate \
95 success unless, at the time the response is given, it intends to delete \
96 the resource or move it to an inaccessible location.