Http error codes



  • Error or Status Code Description

    100 Series

    Informational - These status codes indicate a provisional response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.

    100

    Continue.

    101

    Switching protocols.

    200 Series

    Success - This class of status codes indicates that the server successfully accepted the client request.

    200

    The client request has succeeded. This status code indicates that the Web server has successfully processed the request.

    201

    Created.

    202

    Accepted.

    203

    Non-authoritative information.

    204

    No content.

    205

    Reset content.

    206

    Partial content.

    300 Series

    Redirection - The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server or repeat the request by using a proxy server.

    302

    Object moved.

    304

    Not modified. The client requests a document that is already in its cache and the document has not been modified since it was cached. The client uses the cached copy of the document, instead of downloading it from the server

    307

    Temporary redirect.

    400 Series

    Client Error - An error occurs, and the client appears to be at fault. For example, the client may request a page that does not exist, or the client may not provide valid authentication information.

    400

    Bad request.

    401

    Access denied.

    401.1

    Logon failed. The logon attempt is unsuccessful, probably because of a user name or password that is not valid.

    401.2

    Logon failed due to server configuration.

    401.3

    Unauthorized due to ACL on resource. This indicates a problem with NTFS permissions. This error may occur even if the permissions are correct for the file that you are trying to access. For example, you see this error if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory.

    401.4

    Authorization failed by filter.

    401.5

    Authorization failed by ISAPI/CGI application.

    401.7

    Access denied by URL authorization policy on the Web server. This error code is specific to IIS 6.0.

    403

    Forbidden.

    403.1

    Execute access forbidden. The following are two common causes of this error message:

    • You do not have enough Execute permissions. For example, you may receive this error message if you try to access an ASP page in a directory where permissions are set to None, or you try to execute a CGI script in a directory with Scripts Only permissions.
    • The script mapping for the file type that you are trying to execute is not set up to recognize the verb that you are using (for example, GET or POST).

    403.2

    Read access forbidden. Verify that you have Read access to the directory. Also, if you are using a default document, verify that the document exists.

    403.3

    Write access forbidden. Verify that you have Write access to the directory

    403.4

    SSL required. Use HTTPS instead of HTTP to access the page.

    403.5

    SSL 128 required.

    403.6

    IP address rejected.

    403.7

    Client certificate required. You do not have a valid client certificate installed

    403.8

    Site access denied.

    403.9

    Too many users. The number of users who are connected to the server exceeds the connection limit.

    403.10

    Invalid configuration.

    403.11

    Password change.

    403.12

    Mapper denied access. The page that you want to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied access to the file.

    403.13

    Client certificate revoked.

    403.14

    Directory listing denied.

    403.15

    Client Access Licenses exceeded.

    403.16

    Client certificate is untrusted or invalid.

    403.17

    Client certificate has expired or is not yet valid.

    403.18

    Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0.

    403.19

    Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.

    403.20

    Passport logon failed. This error code is specific to IIS 6.0.

    404

    Not found. This error may occur if the file that you are trying to access has been moved or deleted.

    404.0

    File or directory not found.

    404.1

    Web site not accessible on the requested port.

    404.2

    Web service extension lockdown policy prevents this request.

    404.3

    MIME map policy prevents this request.

    405

    HTTP verb used to access this page is not allowed (method not allowed).

    406

    Client browser does not accept the MIME type of the requested page.

    407

    Proxy authentication required.

    412

    Precondition failed.

    413

    Request entity too large.

    414

    Request-URL too long.

    415

    Unsupported media type.

    416

    Requested range not satisfiable.

    417

    Execution failed.

    423

    Locked error.

    500 Series

    Server Error - The server cannot complete the request because it encounters an error.

    500

    Internal server error. You see this error message for a wide variety of server-side errors.

    500.12

    Application is busy restarting on the Web server. Indicates that you tried to load an ASP page while IIS was in the process of restarting the application. This message should disappear when you refresh the page. If you refresh the page and the message appears again, it may be caused by antivirus software that is scanning your Global.asa file.

    500.13

    Web server is too busy.

    500.15

    Direct requests for Global.asa are not allowed.

    500.16

    UNC authorization credentials incorrect. This error code is specific to IIS 6.0.

    500.18

    URL authorization store cannot be opened. This error code is specific to IIS 6.0.

    500.100

    Internal ASP error. You receive this error message when you try to load an ASP page that has errors in the code.

    501

    Header values specify a configuration that is not implemented.

    502

    Bad Gateway. Web server received an invalid response while acting as a gateway or proxy. You receive this error message when you try to run a CGI script that does not return a valid set of HTTP headers.

    502.1

    CGI application timeout.

    502.2

    Error in CGI application.

    503

    Service unavailable. This error code is specific to IIS 6.0.

    504

    Gateway timeout.

    505

    HTTP version not supported.


Log in to reply
 



Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • To try spamarrest for yourself visit the following link:

    Spamarrest email privacy

    read more
  • @SusanJaneW Spamarrest email easy setup

    INCOMING SERVER Server mail.spamarrest.com Server Type POP or IMAP Username Your Spam Arrest Username Password Your Spam Arrest Password``` <<--------------------------------------------------------------->> OUTGOING SERVER Server smtp.spamarrest.com Username* Your Spam Arrest Username Password* Your Spam Arrest Password Server Port 25, 587, or 2525

    read more
});