Umbraco application with cookie hosted on Azure App GW doesn't work via WAF V2

Manjunatha Munireddy 1 Reputation point
2023-08-01T05:48:35.4866667+00:00

Hello,

Our customer is using Application Developed in Umbraco 10.

This Application URL is configured to access over public/internet via Azure Application Gateway WAF V2.

But umbraco backoffice doesn't work as expected, when we login to application, it just gives blank page.

UMB_UCONTEXT_C and values are alphanumeric with special characters and having (_) and (-) as well.
A similar type of issue has been reported here
https://github.com/MicrosoftDocs/azure-docs/issues/94465

  • I have the listener created “xyz.com-443” on azure app gw
  • I have created a local host entry for DNS resolution pointing to my azure app gw WAF V2 public IP
  • This listener has the WAF policy mapped “xyz.com-wafpolicy01”
  • WAF Policy is in prevention mode
  • I have reviewed the WAF logs and allowed the URI’s and application related cookies and requests, post reviewing the WAF logs
  • Now I don’t see anything getting blocked on WAF policy (Azure App GW logs)
  • But Still the URL https://xyz.com/umbraco application if i login, it is giving me blank page
  • There are few article that I have referred, https://github.com/MicrosoftDocs/azure-docs/issues/94465 and https://github.com/umbraco/Umbraco-CMS/issues/12580
  • I have tried putting the WAF policy into Detection mode and Disable it, But still no luck

Any Workaround or suggestion on this issue ?

Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
1,213 questions
Azure Web Application Firewall
{count} votes

1 answer

Sort by: Most helpful
  1. KapilAnanth-MSFT 49,536 Reputation points Microsoft Employee Moderator
    2023-08-29T14:03:07.6266667+00:00

    @Manjunatha Munireddy

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I see that you have reached out to Azure Support and they have provided an analysis of your environment.

    From their observation,

    Request header names containing other characters are discarded when a request is sent to the backend target. Response header names can contain any alphanumeric characters and specific symbols as defined in RFC 7230, except for underscores (_).

    Please let us know if we can be of any further assistance here.

    Thanks,

    Kapil


    Please Accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.