IBM E02HRLL-G Administration Guide - Page 101

Series, Request URI Too Large

Page 101 highlights

The server has not found anything matching the requested URL. This file doesn't exist. This is the message you get if you type bad URL into your browser. This can also be sent if the server has been told to protect the document by telling unauthorized people that it does not exist. 404 errors are the result of requests for pages which do not exist, and can come from: - A URL typed incorrectly - A bookmark which points to a file that is no longer there - Search engines looking for a robots.txt file (which is used to mark pages that are not to be indexed by search engines) - Users guessing file names - Bad links from your site or other sites v 405 - Method Not Allowed The method specified in the request line cannot be used for the resource identified by the request URL. v 406 - None Acceptable The server has found a resource matching the request URL, but not one that satisfies the conditions identified by the Accept and Accept-Encoding request headers. v 407 - Proxy Authentication Required This code is reserved for future use. It is similar to 401 (Unauthorized) but indicates that the client must first authenticate itself with a proxy. HTTP 1.0 does not provide a means for proxy authentication. v 408 - Request Time Out The client did not produce a request within the time the server was prepared to wait. v 409 - Conflict The request might not be completed because of a conflict with the current state of the resource. v 410 - Gone The requested resource is no longer available at the server and no forwarding address is known. v 411 - Authorization Refused The request credentials provided by the client were rejected by the server or were insufficient to grant authorization to access the resource. v 412 - Precondition Failed v 413 - Request Entity Too Large v 414 - Request URI Too Large v 415 - Unsupported Media Type 500 Series v 500 - Internal Server Error The server encountered an unexpected condition that prevented it from filling the request. Something went wrong with the Web server and it cannot give you a meaningful response. There is typically nothing that can be done from the browser end to fix this error; the server administrator checks the error log for the server to see what happened. This is often the error message for a CGI script which has not been properly coded. v 501 - Method Not Implemented Chapter 10. Analyzing document flows 95

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268

The server has not found anything matching the requested URL. This file
doesn’t exist. This is the message you get if you type bad URL into your
browser. This can also be sent if the server has been told to protect the
document by telling unauthorized people that it does not exist. 404 errors are
the result of requests for pages which do not exist, and can come from:
A URL typed incorrectly
A bookmark which points to a file that is no longer there
Search engines looking for a
robots.txt
file (which is used to mark pages
that are not to be indexed by search engines)
Users guessing file names
Bad links from your site or other sites
v
405 - Method Not Allowed
The method specified in the request line cannot be used for the resource
identified by the request URL.
v
406 - None Acceptable
The server has found a resource matching the request URL, but not one that
satisfies the conditions identified by the Accept and Accept-Encoding request
headers.
v
407 - Proxy Authentication Required
This code is reserved for future use. It is similar to 401 (Unauthorized) but
indicates that the client must first authenticate itself with a proxy. HTTP 1.0 does
not provide a means for proxy authentication.
v
408 - Request Time Out
The client did not produce a request within the time the server was prepared to
wait.
v
409 - Conflict
The request might not be completed because of a conflict with the current state
of the resource.
v
410 - Gone
The requested resource is no longer available at the server and no forwarding
address is known.
v
411 - Authorization Refused
The request credentials provided by the client were rejected by the server or
were insufficient to grant authorization to access the resource.
v
412 - Precondition Failed
v
413 - Request Entity Too Large
v
414 - Request URI Too Large
v
415 - Unsupported Media Type
500 Series
v
500 - Internal Server Error
The server encountered an unexpected condition that prevented it from filling
the request. Something went wrong with the Web server and it cannot give you
a meaningful response. There is typically nothing that can be done from the
browser end to fix this error; the server administrator checks the error log for
the server to see what happened. This is often the error message for a CGI script
which has not been properly coded.
v
501 - Method Not Implemented
Chapter 10. Analyzing document flows
95