How to get session value in ashx handler in iOS safari?

Question

0.00/5 (No votes)

See more:

I am calling cross domain from an iFrame, passing username and password from iFrame to cross domain. in cross domain aspx page i got username and password and can set/get session value. Now when I am calling a .ASHX handler from the aspx page, Session values are not being retrieved from handler. it giving null reference error.

What I have tried:

I have used IRequiresSessionState.

--The scenario is happening in iOS safari browser only, rest are working fine.

How to resolve?

Posted 26-Dec-19 18:57pm

Soumen Halder

Updated 27-Dec-19 2:42am

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)

MadMyche · Answer 1 · 2019-12-27T02:42:00

So it looks like iOS Safari is not liking the code that seems to work everywhere else. The best way to find out what it doesn't like then would be to use whatever version of "developer tools" the browser has to see if a script is not being loaded or a component of the iFrame, or something completely different like a problem with cross-domain cookie access.

If it is a cross-domain issue, then it is not unique to you, as S/O has a few questions on this topic also.... I would suggest you read through these and their linked resources to see if one of the presented solutions will work for you.
1: p3p - safari does not allowed cross-domain cookies in iframe - Stack Overflow[^]
2: javascript - Setting cross-domain cookies in Safari - Stack Overflow[^]