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