How do I make this 403 error go away?

Question

0.00/5 (No votes)

See more:

If I add the following code to my web config in the System.Web section. I get a 403 error when trying to connect. Any thoughts?

<sessionState mode="InProc"
   cookieless="true"
   timeout="120"/>

If I remove mode and cookieless flag the site comes up.

What I have tried:

taking it out, searching the web, etc...

Posted 14-Jan-20 8:30am

RmcbainTheThird

Updated 14-Jan-20 22:57pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2020-01-14T22:57:00

If in doubt, look at the error message. A quick google tells you what you need to know:
403 error - Google Search[^]
Error 403 Means "Forbidden" - you don't have permission to access some resource on that page, or the page itself.
At a guess, it's in a folder that requires a user to log in with a specific role, but since we don't have any access to your codebase we can't tell.
Compare that page with a working page (probably in a different folder) and compare the web.config files to see if there is any security info in them.