URL Encoding Reference

URL Encoding Reference - Encode characters

ASCII Character URL-encoding
space %20
! %21
" %22
# %23
$ %24
% %25
& %26
' %27
( %28
) %29
* %2A
+ %2B
, %2C
- %2D
. %2E
/ %2F
0 %30
1 %31
2 %32
3 %33
4 %34
5 %35
6 %36
7 %37
8 %38
9 %39
: %3A
; %3B
< %3C
= %3D
> %3E
? %3F
@ %40
A %41
B %42
C %43
D %44
E %45
F %46
G %47
H %48
I %49
J %4A
K %4B
L %4C
M %4D
N %4E
O %4F
P %50
Q %51
R %52
S %53
T %54
U %55
V %56
W %57
X %58
Y %59
Z %5A
[ %5B
\ %5C
] %5D
^ %5E
_ %5F
` %60
a %61
b %62
c %63
d %64
e %65
f %66
g %67
h %68
i %69
j %6A
k %6B
l %6C
m %6D
n %6E
o %6F
p %70
q %71
r %72
s %73
t %74
u %75
v %76
w %77
x %78
y %79
z %7A
{ %7B
| %7C
} %7D
~ %7E
  %7F
%80
  %81
%82
ƒ %83
%84
%85
%86
%87
ˆ %88
%89
Š %8A
%8B
Π%8C
  %8D
Ž %8E
  %8F
  %90
%91
%92
%93
%94
%95
%96
%97
˜ %98
%99
š %9A
%9B
œ %9C
  %9D
ž %9E
Ÿ %9F
  %A0
¡ %A1
¢ %A2
£ %A3
  %A4
¥ %A5
| %A6
§ %A7
¨ %A8
© %A9
ª %AA
« %AB
¬ %AC
¯ %AD
® %AE
¯ %AF
° %B0
± %B1
² %B2
³ %B3
´ %B4
µ %B5
%B6
· %B7
¸ %B8
¹ %B9
º %BA
» %BB
¼ %BC
½ %BD
¾ %BE
¿ %BF
À %C0
Á %C1
 %C2
à %C3
Ä %C4
Å %C5
Æ %C6
Ç %C7
È %C8
É %C9
Ê %CA
Ë %CB
Ì %CC
Í %CD
Î %CE
Ï %CF
Ð %D0
Ñ %D1
Ò %D2
Ó %D3
Ô %D4
Õ %D5
Ö %D6
  %D7
Ø %D8
Ù %D9
Ú %DA
Û %DB
Ü %DC
Ý %DD
Þ %DE
ß %DF
à %E0
á %E1
â %E2
ã %E3
ä %E4
å %E5
æ %E6
ç %E7
è %E8
é %E9
ê %EA
ë %EB
ì %EC
í %ED
î %EE
ï %EF
ð %F0
ñ %F1
ò %F2
ó %F3
ô %F4
õ %F5
ö %F6
÷ %F7
ø %F8
ù %F9
ú %FA
û %FB
ü %FC
ý %FD
þ %FE
ÿ %FF


URL Encoding Reference

The ASCII device control characters %00-%1f were originally designed to control hardware devices. Control characters have nothing to do inside a URL.

ASCII Character Description URL-encoding
NUL null character %00
SOH start of header %01
STX start of text %02
ETX end of text %03
EOT end of transmission %04
ENQ enquiry %05
ACK acknowledge %06
BEL bell (ring) %07
BS backspace %08
HT horizontal tab %09
LF line feed %0A
VT vertical tab %0B
FF form feed %0C
CR carriage return %0D
SO shift out %0E
SI shift in %0F
DLE data link escape %10
DC1 device control 1 %11
DC2 device control 2 %12
DC3 device control 3 %13
DC4 device control 4 %14
NAK negative acknowledge %15
SYN synchronize %16
ETB end transmission block %17
CAN cancel %18
EM end of medium %19
SUB substitute %1A
ESC escape %1B
FS file separator %1C
GS group separator %1D
RS record separator %1E
US unit separator %1F

Keywords:

Filed Under: Java

Database Standards & Guidelines

General

  • Primary keys should not be specified for tables, unique indexes should be used instead
  • For partitioned tables, unique indexes must include the partition key
  • Type tables should be suffixed with _TYPE
  • Objects should be prefixed with their schema in DDL statements (table, index, sequence, etc)
  • Use of CLOB/BLOB datatypes is discouraged
  • Use of functions/procedures/packages is discouraged
  • Always use semicolons (;) to separate statements used in scripts
  • If you're not sure of something, ask. Unwanted database changes can haunt you forever.

Table Creation/Alter

  • UUID columns should always be CHAR(36), not VARCHAR2(36) or similar
  • Sample Create:
    	CREATE TABLE QBW.DISPOSITION(  ID            CHAR(36 BYTE)                   NOT NULL,  DISP_LINK_ID  CHAR(36 BYTE)                   NOT NULL,  PROC_DATE     DATE                            NOT NULL,  DISP_DATA     VARCHAR2(4000 BYTE),  DISP_DATE     DATE                            NOT NULL,  LINK_TYPE_ID  INTEGER                         NOT NULL,  DISP_TYPE_ID  INTEGER                         NOT NULL);
    	
  • Sample Alter (column add):
    • ALTER TABLE QBW.disposition ADD correlation_id CHAR(36);
  • Sample Alter (column drop):
    • ALTER TABLE QBW.disposition DROP COLUMN correlation_id;

Index Creation

  • For partitioned tables, the partition key is generally unnecessary in normal indexes.
  • Unique Index Sample:
    • CREATE UNIQUE INDEX QBW.DISP_UNIQUE_INDX ON QBW.DISPOSITION (ID, PROC_DATE);
  • Normal Index Sample:
    	CREATE INDEX QBW.disp_link_type_date_idx ON QBW.disposition(disp_link_id, disp_type_id, proc_date);
    	

Synonym Creation

  • Create public, not private, synonyms
  • Sample:
    • CREATE OR REPLACE PUBLIC SYNONYM DISPOSITION FOR QBW.DISPOSITION;

Sequence Creation

  • Generally try to avoid the use of sequences as it is vendor specific functionality  (It's better to use GUID) 
  • Sequences normally only need the SELECT grant. However, if allowed, ALTER is also handy
  • When used, sequences in DR databases should be created at an offset (i.e. production uses even sequences, dr uses odd)
  • Sample:
    	CREATE SEQUENCE QBW.SOME_SEQ  START WITH 1  INCREMENT BY 2  MAXVALUE 9999999999  MINVALUE 1  CYCLE  CACHE 1000  NOORDER;
    	

Grants

  • SELECT, INSERT, UPDATE, DELETE privileges should be granted to QBW_ROLE
  • SELECT privileges should be granted to QBW_RONLY
  • Sample
    • GRANT SELECT, INSERT, UPDATE, DELETE ON QBW.DISPOSITION TO QBW_ROLE;
    • GRANT SELECT ON DISPOSITION TO QBW_RONLY;

Keywords:

Filed Under: MySQL

List of HTTP status codes

The HTTP status codes

This section describes the HTTP status codes that IIS 7.0 uses.

Note This article does not list every possible HTTP status code as dictated in the HTTP specification. This article includes only the HTTP status codes that IIS 7.0 can send. For example, a custom Internet Server API (ISAPI) filter or a custom HTTP module can set its own HTTP status code.

1xx - Informational

These HTTP status codes indicate a provisional response. The client computer receives one or more 1xx responses before the client computer receives a regular response.

IIS 7.0 uses the following informational HTTP status codes:
  • 100 - Continue.
  • 101 - Switching protocols.

2xx - Success

These HTTP status codes indicate that the server successfully accepted the request.

IIS 7.0 uses the following success HTTP status codes:
  • 200 - OK. The client request has succeeded.
  • 201 - Created.
  • 202 - Accepted.
  • 203 - Nonauthoritative information.
  • 204 - No content.
  • 205 - Reset content.
  • 206 - Partial content.

3xx - Redirection

These HTTP status codes indicate that the client browser must take more action to fulfill the request. For example, the client browser may have to request a different page on the server. Or, the client browser may have to repeat the request by using a proxy server.

IIS 7.0 uses the following redirection HTTP status codes:
  • 301 - Moved permanently.
  • 302 - Object moved.
  • 304 - Not modified.
  • 307 - Temporary redirect.

4xx - Client error

These HTTP status codes indicate that an error occurred and that the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist. Or, the client browser may not have provided valid authentication information.

IIS 7.0 uses the following client error HTTP status codes:
  • 400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.

    IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 400 error:
    • 400.1 - Invalid Destination Header.
    • 400.2 - Invalid Depth Header.
    • 400.3 - Invalid If Header.
    • 400.4 - Invalid Overwrite Header.
    • 400.5 - Invalid Translate Header.
    • 400.6 - Invalid Request Body.
    • 400.7 - Invalid Content Length.
    • 400.8 - Invalid Timeout.
    • 400.9 - Invalid Lock Token.
  • 401 - Access denied.

    IIS 7.0 defines several HTTP status codes that indicate a more specific cause of a 401 error. The following specific HTTP status codes are displayed in the client browser but are not displayed in the IIS log:
    • 401.1 - Logon failed.
    • 401.2 - Logon failed due to server configuration.
    • 401.3 - Unauthorized due to ACL on resource.
    • 401.4 - Authorization failed by filter.
    • 401.5 - Authorization failed by ISAPI/CGI application.
  • 403 - Forbidden.

    IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 403 error:
    • 403.1 - Execute access forbidden.
    • 403.2 - Read access forbidden.
    • 403.3 - Write access forbidden.
    • 403.4 - SSL required.
    • 403.5 - SSL 128 required.
    • 403.6 - IP address rejected.
    • 403.7 - Client certificate required.
    • 403.8 - Site access denied.
    • 403.9 - Forbidden: Too many clients are trying to connect to the Web server.
    • 403.10 - Forbidden: Web server is configured to deny Execute access.
    • 403.11 - Forbidden: Password has been changed.
    • 403.12 - Mapper denied access.
    • 403.13 - Client certificate revoked.
    • 403.14 - Directory listing denied.
    • 403.15 - Forbidden: Client access licenses have exceeded limits on the Web server.
    • 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.
    • 403.19 - Cannot execute CGI applications for the client in this application pool.
    • 403.20 - Forbidden: Passport logon failed.
    • 403.21 - Forbidden: Source access denied.
    • 403.22 - Forbidden: Infinite depth is denied.
  • 404 - Not found.

    IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 404 error:
    • 404.0 - Not found.
    • 404.1 - Site Not Found.
    • 404.2 - ISAPI or CGI restriction.
    • 404.3 - MIME type restriction.
    • 404.4 - No handler configured.
    • 404.5 - Denied by request filtering configuration.
    • 404.6 - Verb denied.
    • 404.7 - File extension denied.
    • 404.8 - Hidden namespace.
    • 404.9 - File attribute hidden.
    • 404.10 - Request header too long.
    • 404.11 - Request contains double escape sequence.
    • 404.12 - Request contains high-bit characters.
    • 404.13 - Content length too large.
    • 404.14 - Request URL too long.
    • 404.15 - Query string too long.
    • 404.16 - DAV request sent to the static file handler.
    • 404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.
  • 405 - Invalid verb.
  • 406 - Client browser does not accept the MIME type of the requested page.
  • 408 - Request timed out.
  • 412 - Precondition failed.

5xx - Server error

These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

IIS 7.0 uses the following server error HTTP status codes:
  • 500 - Internal server error.

    IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 500 error:
    • 500.0 - Module or ISAPI error occurred.
    • 500.11 - Application is shutting down on the Web server.
    • 500.12 - Application is busy restarting on the Web server.
    • 500.13 - Web server is too busy.
    • 500.15 - Direct requests for Global.asax are not allowed.
    • 500.19 - Configuration data is invalid.
    • 500.21 - Module not recognized.
    • 500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
    • 500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
    • 500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
    • 500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
      Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
    • 500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
      Note Here is where the global rules configuration is read.
    • 500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
    • 500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
    • 500.100 - Internal ASP error.
  • 501 - Header values specify a configuration that is not implemented.
  • 502 - Web server received an invalid response while acting as a gateway or proxy.

    IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 502 error:
    • 502.1 - CGI application timeout.
    • 502.2 - Bad gateway.
  • 503 - Service unavailable.

    IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 503 error:
    • 503.0 - Application pool unavailable.

    http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1.1

Keywords:

Filed Under: HTML Basic

Image transition

Keywords:

Filed Under:

RSA encrypt

Keywords:

Filed Under: Java

TextBox widget example - adding any formatted HTML code to the widget.

Comment List

  • None

Month List