April 2018

Resolution: #ff6699ff #FF6699FF Same, case insensitive)

#ff6699ff from # It is composed of eight numbers or letters, the first two ff Transparency (hexadecimal), the last six digits ffffff Color code, RGB color matching (hexadecimal)

HTML online color picker: HTML Color Picker

The source code for this website comes from GitHub: evol.colorpicker

Source code download: evol.colorpicker

Transparency Reference Table

-Read the rest-

The HTTP response status code indicates a specific HTTP Whether the request completed successfully. Responses are divided into five categories: information response, successful response, redirection, client error and server error. Status codes are defined by section 10 of RFC 2616 definition

Information response

100 Continue
This temporary response shows that everything so far is feasible, and the client should continue to request. If it has been completed, it will be ignored.
101 Switching Protocol
This code responds to the client's Upgrade Header and indicates that the server is also switching.
102 Processing ( WebDAV )
This code indicates that the server has received and is processing the request, but no response is available.

Successful response

200 OK

The request was successful. The meaning of success depends on the HTTP method:



  • GET: The resource has been extracted and transmitted in the message body.
  • HEAD: The entity header is located in the message body.
  • POST: The resource describing the action result is transmitted in the message body.
  • TRACE: The message body contains the request message received by the server
201 Created
The request was successful and a new resource was created as a result. This is usually the response sent after the PUT request.
202 Accepted
The request has been received but has not yet been responded to. There is no result. It means that there will not be an asynchronous response to indicate the result of the current request, and other processes and services are expected to process the request, or batch processing.
203 Non-Authoritative Information
The server has successfully processed the request, but the returned entity header meta information is not a valid set on the original server, but a copy from the local or a third party. The current information may be a subset or superset of the original version. For example, metadata containing resources may cause the original server to know the superset of meta information. It is not necessary to use this status code, and it is only appropriate if the response will return 200 OK without using this status code.
204 No Content
The server successfully processes the request, but does not need to return any entity content, and wants to return updated meta information. The response may return new or updated meta information in the form of entity headers. If such header information exists, it should correspond to the requested variable. If the client is a browser, the user browser should retain the page that sent the request without any change in the document view, even if the new or updated meta information should be applied to the document in the active view of the user browser according to the specification. Since the 204 response is prohibited from containing any message body, it always ends with the first empty line after the message header.
205 Reset Content
The server successfully processed the request and returned nothing. However, unlike the 204 response, the response that returns this status code requires the requester to reset the document view. This response is mainly used to reset the form immediately after receiving user input, so that the user can easily start another input. Like the 204 response, the response is also prohibited from containing any message body and ends with the first empty line after the message header.
206 Partial Content
The server has successfully processed some GET requests. HTTP download tools like FlashGet or Thunderbolt use this type of response to achieve breakpoint resume or to break a large document into multiple download segments for simultaneous download. The request must contain the Range header information to indicate the content range the client wants, and may contain If Range as the request condition
207 Multi-Status ( WebDAV )
The status code extended by WebDAV (RFC 2518) represents that the following message body will be an XML message, and may contain a series of independent response codes according to the number of previous sub requests.
208 Multi-Status ( WebDAV )
The: propstat response element is used in DAV to avoid repeatedly enumerating internal members of multiple bindings to the same collection.
226 IM Used ( HTTP Delta encoding )
The server has completed the GET request for resources, and the response is a representation of the operation results of one or more instances of the current instance application.

redirect

300 Multiple Choice
The requested resource has a series of feedback information to choose from, each with its own specific address and browser driven consultation information. Users or browsers can choose a preferred address for redirection.
301 Moved Permanently
The requested resource has been permanently moved to a new location, and any future reference to this resource should use one of the several URIs returned by this response. If possible, the client with link editing function should automatically change the requested address to the one fed back from the server. Unless otherwise specified, this response is also cacheable.
302 Found
The requested resource now responds to the request temporarily from a different URI. Since such redirection is temporary, the client should continue to send future requests to the original address. This response is cacheable only when specified in Cache Control or Expires.
303 See Other
The response corresponding to the current request can be found on another URI, and the client should use GET to access that resource. This method exists mainly to allow the output of POST requests activated by scripts to be redirected to a new resource.
304 Not Modified
If the client sends a GET request with conditions and the request is allowed, but the content of the document (since the last access or according to the conditions of the request) has not changed, the server should return this status code. 304 The response must not contain the message body, so it always ends with the first empty line after the message header.
305 Use Proxy
The requested resource can only be accessed through the specified proxy. The URI information of the specified proxy will be given in the Location field, and the receiver needs to repeatedly send a separate request, through which the corresponding resource can be accessed. Only the original server can establish a 305 response.
306 unused
In the latest version of the specification, 306 status code is no longer used.
307 Temporary Redirect
The requested resource now responds to the request temporarily from a different URI. Since such redirection is temporary, the client should continue to send future requests to the original address. This response is cacheable only when specified in Cache Control or Expires.
308 Permanent Redirect
This means that the resource is now permanently located by Location: Another URI specified by the HTTP Response header. This is related to 301 Moved Permanently HTTP The response code has the same semantics, but the user agent cannot change the HTTP method used: if used in the first request POST Must be used in the second request POST

Client response

400 Bad Request
1. Semantic error. The current request cannot be understood by the server. Unless modified, the client should not submit this request repeatedly.
2. The request parameters are incorrect.
401 Unauthorized
The current request requires user authentication. The response must contain a WWW Authenticate header for the requested resource to query the user information. The client can repeatedly submit a request containing the appropriate Authorization header information. If the current request already contains the Authorization certificate, the 401 response represents that the server has rejected those certificates. If the 401 response contains the same authentication query as the previous response, and the browser has tried authentication at least once, the browser should show the user the entity information contained in the response, because the entity information may contain relevant diagnostic information.
402 Payment Required
This response code is reserved for future use. The original purpose of creating this response code is to be used in digital payment systems, but it is not used now.
403 Forbidden
The server understood the request, but refused to execute it. Unlike 401 responses, authentication does not provide any help, and the request should not be submitted repeatedly. If this is not a HEAD request, and the server wants to be able to explain why the request cannot be executed, then the reason for rejection should be described in the entity. Of course, the server can also return a 404 response if it does not want the client to get any information.
404 Not Found
The request failed. The resource that the request wanted was not found on the server. No information can tell the user whether the situation is temporary or permanent. If the server knows the situation, it should use the 410 status code to tell the old resource that it is permanently unavailable due to some internal configuration mechanism problems, and there is no address to jump to. The status code 404 is widely used when the server does not want to reveal why the request was rejected or no other suitable response is available.
405 Method Not Allowed
The request method specified in the request line cannot be used to request the corresponding resource. The response must return an Allow header to indicate the list of request methods that the current resource can accept. Because PUT and DELETE methods will write to the resources on the server, most web servers do not support or do not allow the above request methods in the default configuration, and 405 errors will be returned for such requests.
406 Not Acceptable
The content characteristics of the requested resource cannot meet the conditions in the request header, so the response entity cannot be generated.
407 Proxy Authentication Required
Similar to the 401 response, except that the client must authenticate on the proxy server. The proxy server must return a Proxy Authenticate for identity inquiry. The client can return a Proxy Authorization header for verification.
408 Request Timeout
The request timed out. The client did not complete sending a request within the server's waiting time. The client can submit this request again at any time without making any changes.
409 Conflict
The request could not be completed because of a conflict with the current state of the requested resource. This code can only be used when the user is considered to be able to resolve the conflict and resubmit a new request. The response should contain enough information for the user to find the source of the conflict.
410 Gone
The requested resource is no longer available on the server, and there is no known forwarding address. Such a situation should be considered permanent. If possible, the client with link editing function should delete all references to this address after obtaining user permission. If the server does not know or cannot determine whether the condition is permanent, then the 404 status code should be used. Unless otherwise specified, this response is cacheable.
411 Length Required
The server refuses to use the Content-Length Header. The valid length of the request message body is added Content-Length After the header, the client can submit the request again.
412 Precondition Failed
The server failed to meet one or more of the prerequisites given in the request header field during verification. This status code allows the client to set preconditions in the requested meta information (request header field data) when acquiring resources, so as to avoid the request method being applied to resources other than the content it wants.
413 Payload Too Large
The server refuses to process the current request because the size of the entity data submitted by the request exceeds the range that the server is willing or able to process. In this case, the server can close the connection to prevent the client from continuing to send the request. If this condition is temporary, the server should return a Retry-After To tell the client how long it can try again.
414 URI Too Long
The requested URI length exceeds the length that the server can interpret, so the server refused to service the request. This is relatively rare. Common situations include that the form submission that should have used the POST method has changed to the GET method, resulting in an excessively long query string.
415 Unsupported Media Type
For the currently requested method and requested resource, the entity submitted in the request is not in the format supported by the server, so the request is rejected.
416 Requested Range Not Satisfiable
If the request contains a Range request header, and any data range specified in the Range does not coincide with the available range of the current resource, and if the If Range request header is not defined in the request, the server should return a 416 status code.
417 Expectation Failed
This response code means that the server cannot meet expect The expected value indicated by the request header field.
418 I'm a teapot
Server refused to try Teapot brews coffee
412 Precondition Failed
The request is for a server that cannot respond. This can be sent by the server, which is not configured to respond to a combination of schemes and permissions contained in the request URI.
422 Unprocessable Entity ( WebDAV )
The request format is good, but cannot be followed due to semantic errors.
423 Locked ( WebDAV )
The resource being accessed is locked.
424 Failed Dependency ( WebDAV )
This request failed because the previous request failed.
426 Upgrade Required
The server refuses to execute the request using the current protocol, but may be willing to do so after the client is upgraded to another protocol. Server sends in 426 response Upgrade Header to indicate the required protocol.
428 Precondition Required
The original server requires that the request be conditional. To prevent "missing updates", that is, the client gets the resource status, modifies the status and returns it to the server, and the third party modifies the status on the server, which leads to conflicts.
429 Too Many Requests
The user sent too many requests in the given time ("Limit request rate").
431 Request Header Fields Too Large
The server is unwilling to process the request because its request header fields are too large. The request can be resubmitted after reducing the size of the request header field.
451 Unavailable For Legal Reasons
Users request illegal resources, such as web pages reviewed by the government.

Server response

500 Internal Server Error
The server encountered a situation that it did not know how to handle.
501 Not Implemented
This request method is not supported by the server and cannot be processed. only GET and HEAD It is required that the server support it. They will not return this error code.
502 Bad Gateway
This error response indicates that the server, as the gateway, needs to get a response to handle the request, but gets an error response.
503 Service Unavailable
The server is not ready to process the request. The common reason is that the server is down due to maintenance or overloading. Please note that along with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and Retry-After : If possible, the HTTP header should contain the estimated time before service recovery. The webmaster must also pay attention to the cache related headers sent with this response, because these temporary condition responses should not normally be cached.
504 Gateway Timeout
This error code is returned when the server, as the gateway, cannot get a response in time.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates
The server has an internal configuration error: the transparent content negotiation of the request results in a circular reference.
507 Insufficient Storage
The server has an internal configuration error: the selected variant resource is configured to participate in transparent content negotiation itself, so it is not an appropriate endpoint in the negotiation process.
508 Loop Detected ( WebDAV )
The server detected an infinite loop while processing the request.
The server detected an infinite loop while processing the request.
510 Not Extended
The server needs to expand the request further to implement it.
511 Network Authentication Required
The 511 status code indicates that the client needs authentication to obtain network access.

preface

2018-04-24 17:33 update code

In order to facilitate Fusion APP Developers can easily check whether the APP is updated and authorized. I did this Authorization/Upgrade Management System , you don't need to build your own server, you just need to aus.nowtime.cc Register an account and log in, then add APP

usage method

1. Register and log in the account

I won't go into details about this, Registration account - authorization/upgrade management system

-Read the rest-