Different behavior between Edge, Chrome, Firefox, IE-Mode and IE

MiBe67 1

Hello,

in my company I run a 20 year old web application (aspx) on the side.
The main page is divided by iFrames and authentication mode="Forms" is set in the Web.config.
Now I have the following problem. When I open the page in Firefox, Internet Explorer or Edge's Internet Explorer mode, it displays correctly.
If I try this with Edge or Chrome, I get "404 - File or directory not found" in every iFrame.
I would be grateful for any hint that I can use to solve this problem.

Many thanks in advance

Lan Huang-MSFT 25,391 Reputation points Microsoft Vendor

2022-07-27T09:35:08.687+00:00

Hi @MiBe67 ,

HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the URL and make sure that it is spelled correctly.

I think it might be a problem with iFrame.src . Try giving a more specific src . Because Internet Explorer can sometimes fix small bugs in code that other browsers can't.
There may be other issues as well, maybe you can provide more detailed information, preferably a small example that reproduces the problem.
Best regards,
Lan Huang
MiBe67 1 Reputation point

2022-07-27T12:51:24.873+00:00

Hi Lan Huang,

thank you for your prompt reply.

My main page is called main.aspx. It has 3 iFrames named "header", "navi" and "content".
For "header" I point to "Header.aspx" in src. For "navi" I point to "Links.aspx" in src. For "content" I point to "Startseite.aspx" in src.
These 3 pages are in the same directory as main.aspx.

The problem occurs every time main.aspx is opened with Edge or Chrome.

According to an entry in a log file, it looks as if the user information (User.Identity.Name, User.Identity.IsAuthenticated) is lost in Edge and Chrome.

This doesn't happen with Internet Explorer and Firefox.

Best regards,
Michael
AgaveJoe 26,186 Reputation points

2022-07-27T13:26:20.1+00:00

Open the browser's dev tools (press F12). Open the Network view then try accessing main.aspx. Dev tool will show any 404 errors. Click on the error and view the request URL. Compare the Request URL with what you expect. Copy the Request URL from dev tools and paste it into your browser's address bar and see if a 404 is returned.

The error should also contain the Requested URL.

I created a simple test and the iframe worked as expected in Chrome and Edge.

Also, if you can post sample code that reproduces this behavior that we us figure out what's happening.
MiBe67 1 Reputation point

2022-07-27T15:55:10.413+00:00

Thanks for the tip about the dev tools AgaveJoe.

With the tool I found out that Edge performs a redirect when calling up the pages in the iFrames.
With this redirect, the LoginUrl of the forms authentication from web.config is used.
This URL is incorrect. If I understand correctly, the reason for using this URL is a missing authentication.
But I don't understand where this is lost because main.aspx cannot be opened without authentication.
The redirect does not happen with Firefox or Internet Explorer.

Best regards,
Michael
Lan Huang-MSFT 25,391 Reputation points Microsoft Vendor

2022-07-28T07:58:02.61+00:00

Hi @MiBe67 ,
Are there currently only errors pointing to "main.aspx"?
You can try running it in private mode and see if there is an error message.
Can you provide the code so that we can better help you solve the problem?
Best regards,
Lan Huang
MiBe67 1 Reputation point

2022-07-28T14:36:26.437+00:00

Hello, everyone,

thanks to the hints I found a solution.
I had to set <httpCookies requireSSL="true" and "sameSite="None" /> in web.config within <system.web>

Many thanks for the help.