Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Ad icon
Video Content Creator
pramukag
Updated:
Sunday at 6:10 AM
Ad icon
QA Engineer Intern
pramukag
Updated:
Sunday at 6:07 AM
Ad icon
Sell your Land, House on idamata.lk for FREE
sajith.xp.pk
Updated:
Thursday at 9:03 AM
Handmade Character Soft Toys
anil1961
Updated:
Jun 23, 2026
Bodim.lk out now !
Manoj Suranga Bandara
Updated:
Jun 21, 2026
Electronics
Vehicles
Property
Search
Reply to thread
Forums
General
ElaKiri Talk!
Adults sites blocked!!!
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="SIRUS3001" data-source="post: 3158403" data-attributes="member: 74873"><p>The <strong>403 Forbidden</strong> <a href="http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol" target="_blank">HTTP</a> <a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes" target="_blank">status code</a> indicates that the client was able to communicate with the server, but the server doesn't let the user access what was requested.</p><p> An example of descriptive English text that can often accompany such a response is <em>You don't have permission to access /<a href="http://en.wikipedia.org/wiki/Foo" target="_blank">foo</a> on this server.</em></p><p> This indicates a fundamental access problem, which may be difficult to resolve, because the HTTP protocol allows the Web server to give this response without providing any reason at all. So the 403 error is equivalent to a blanket 'NO' by your Web server - with no further discussion allowed, and according to the RFC specifications, with a 403 error code, the request should not be repeated.</p><p> This response may indicate a resource that requires authentication, such as <a href="http://en.wikipedia.org/wiki/Basic_access_authentication" target="_blank">basic access authentication</a> or <a href="http://en.wikipedia.org/wiki/Digest_access_authentication" target="_blank">digest access authentication</a> through the Authorization request <a href="http://en.wikipedia.org/wiki/HTTP_header" target="_blank">header</a>, or some other form of authentication which is managed through user scripts in a programming language such as <a href="http://en.wikipedia.org/wiki/PHP" target="_blank">PHP</a>. However, this use is incorrect, as the HTTP specification states that 403 should only be used when authorization will not help. The 401 Unauthorized code is a better choice for this situation.</p><p> This response is returned by the <a href="http://en.wikipedia.org/wiki/Apache_HTTP_Server" target="_blank">Apache</a> web server when directory listings have been turned off. Microsoft <a href="http://en.wikipedia.org/wiki/Internet_Information_Services" target="_blank">IIS</a> responds in the same way when <a href="http://en.wikipedia.org/wiki/Active_Directory" target="_blank">Active Directory</a> listings are denied.</p></blockquote><p></p>
[QUOTE="SIRUS3001, post: 3158403, member: 74873"] The [B]403 Forbidden[/B] [URL="http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol"]HTTP[/URL] [URL="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes"]status code[/URL] indicates that the client was able to communicate with the server, but the server doesn't let the user access what was requested. An example of descriptive English text that can often accompany such a response is [I]You don't have permission to access /[URL="http://en.wikipedia.org/wiki/Foo"]foo[/URL] on this server.[/I] This indicates a fundamental access problem, which may be difficult to resolve, because the HTTP protocol allows the Web server to give this response without providing any reason at all. So the 403 error is equivalent to a blanket 'NO' by your Web server - with no further discussion allowed, and according to the RFC specifications, with a 403 error code, the request should not be repeated. This response may indicate a resource that requires authentication, such as [URL="http://en.wikipedia.org/wiki/Basic_access_authentication"]basic access authentication[/URL] or [URL="http://en.wikipedia.org/wiki/Digest_access_authentication"]digest access authentication[/URL] through the Authorization request [URL="http://en.wikipedia.org/wiki/HTTP_header"]header[/URL], or some other form of authentication which is managed through user scripts in a programming language such as [URL="http://en.wikipedia.org/wiki/PHP"]PHP[/URL]. However, this use is incorrect, as the HTTP specification states that 403 should only be used when authorization will not help. The 401 Unauthorized code is a better choice for this situation. This response is returned by the [URL="http://en.wikipedia.org/wiki/Apache_HTTP_Server"]Apache[/URL] web server when directory listings have been turned off. Microsoft [URL="http://en.wikipedia.org/wiki/Internet_Information_Services"]IIS[/URL] responds in the same way when [URL="http://en.wikipedia.org/wiki/Active_Directory"]Active Directory[/URL] listings are denied. [/QUOTE]
Insert quotes…
Verification
Asuwa dahayen wadi kalama keeyada?
Post reply
Top
Bottom