Support Thread

IE10 Registration issue

📅 👤 ASP Playground
IE10 Registration issue — APG vNext Guide

This archived support thread addresses IE10 Registration issue. The discussion below documents the reported issue and the steps taken to resolve it.

Troubleshooting Steps

When encountering errors in APG vNext, the following steps help diagnose the problem quickly:

  • Enable detailed errors: Set customErrors mode="Off" in web.config to see the full error message and stack trace.
  • Check the Windows Event Log: Application-level ASP.NET errors are logged in the Windows Event Log under Application.
  • Review the APG error log: Admin Panel → Logs → Error Log shows application-level errors with timestamps.
  • Verify recent changes: If the error appeared after an upgrade or configuration change, roll back or review what changed.

Common Fixes

  • Restart the IIS Application Pool to clear stale state
  • Verify database connectivity and run any pending SQL upgrade scripts
  • Check that all required .NET assemblies are present in the bin folder
  • Clear the ASP.NET temporary files folder (%windir%\Microsoft.NET\Framework\...\Temporary ASP.NET Files)

For further assistance, visit the support forum or review the Knowledge Base.

Internet Explorer 10 Registration Fix

Internet Explorer 10 introduced stricter handling of form submissions and HTTP headers that caused registration issues in APG vNext. The primary symptom was that clicking the Register button appeared to submit the form but the page reloaded without completing registration — no error message was displayed, and the member account was not created. This issue was traced to IE10's handling of CSRF protection tokens and was resolved in APG vNext 4.1.1. If you are on an older version, apply the update or implement the manual fix described below.

Root Cause: Meta X-UA-Compatible

The most common cause of IE10-specific form submission failures in APG vNext was IE10 entering Compatibility View mode, which caused it to emulate IE7 behaviour — bypassing the CSRF token validation mechanism. The fix was to add the X-UA-Compatible meta tag as the first element in the <head> section of the theme layout:

<meta http-equiv="X-UA-Compatible" content="IE=edge">

This tag instructs IE10 and IE11 to use the highest available rendering mode rather than entering compatibility mode based on the document type declaration or intranet zone settings.

Configuring X-UA-Compatible as an HTTP Header

An alternative to adding the meta tag to each page template is to configure the X-UA-Compatible response header at the IIS level, which applies it to all pages served from the application without requiring theme modification. In IIS Manager, select the website → HTTP Response Headers → Add, and enter Name: X-UA-Compatible, Value: IE=edge. This is particularly useful for APG vNext installations that use multiple theme templates, as the header-level configuration covers all templates without requiring the meta tag to be added to each individually.

CSRF Token Handling in Legacy IE

APG vNext uses synchroniser token CSRF protection on all state-changing form submissions — registration, login, profile update, post creation, and admin actions. The token is embedded as a hidden input field in each form and validated server-side on submission. In IE10 Compatibility View mode, the form serialisation sometimes excluded the hidden CSRF token field, causing the server-side validation to reject the submission as a potential CSRF attack — which manifested as a silent page reload rather than an error message to avoid leaking information to potential attackers. The X-UA-Compatible fix prevents IE10 from entering Compatibility View and resolves the token serialisation issue.

Modern Browser Migration Guidance

IE10 was superseded by IE11 in 2013, and IE11 itself reached end-of-life in June 2022. For communities still reporting IE10-related issues, the most practical solution for members is to install Microsoft Edge, which is available as a free download for all supported Windows versions. Edge provides full compatibility with APG vNext and all modern web applications without the IE10/IE11 compatibility issues. For corporate intranet environments where browser upgrades require IT approval, the Compatibility View workaround (X-UA-Compatible header) is still a viable short-term solution while browser standardisation is arranged with the IT department.

Related Resources

Validating the Fix Across Browser Versions

After implementing the X-UA-Compatible fix, validate the registration form across all IE compatibility modes using the IE Developer Tools (F12) → Emulation tab to test in IE10 Document Mode and IE10 Browser Mode. Test the complete registration flow — fill in all required fields, submit the form, verify the confirmation email is sent, and verify the account activates via the email link. Test with the IE compatibility view toggled on and off to confirm the fix works regardless of whether IE is in standard or compatibility mode. For organisations running APG vNext behind a corporate proxy that may override browser compatibility settings, test the registration flow on the actual corporate network with the proxy in place.

Reporting IE10 Issues to APG Support

If the X-UA-Compatible fix does not resolve a specific IE10 form submission issue, file a bug report through the private support forum including the IE10 version number (visible in IE Developer Tools → User Agent String), the specific form that fails, whether the failure occurs only in Compatibility View mode or also in Standard mode, the APG vNext version number, and any JavaScript console errors visible in IE Developer Tools when the form is submitted. The APG support team tests against IE10 Document Mode 10 as the minimum IE compatibility target for older APG vNext releases and can reproduce and investigate version-specific form handling differences with complete reproduction information.

Looking for more help? Browse the support forum or check the Knowledge Base.