Azure / logicapps

Azure Logic Apps labs, samples, and tools
MIT License
368 stars 302 forks source link

The URL generated for HTTP trigger is too long #1233

Open dluc opened 1 week ago

dluc commented 1 week ago

Describe the Bug with repro steps

I'm trying to setup a health check workflow following these instructions: https://learn.microsoft.com/en-us/azure/logic-apps/monitor-health-standard-workflows

The trigger URL is generated after save (actually I need to restart the app), and it looks like this:

https://contoso.p.azurewebsites.net:443/api/health/triggers/httpreq/invoke?api-version=2022-05-01&sp=%2Ftriggers%2Fhttpreq%2Frun&sv=1.0&sig=FOx4fvmwNdEJLDE6ZUXGDDAQJhb8EA-IteTzTXlZfMA

The problem is that the URL path is too long, 144 chars, and the health check allows only up to 65 chars.

Requests to /api/health/triggers/httpreq/invoke?api-version=2022-05-01&sp=%2Ftriggers%2Fhttpreq%2Frun&sv=1.0&sig=FOx4fvmwNdEJLDE6ZUXGDDAQJhb8EA-IteTzTXlZfMA return 200 OK. Requests to /api/health/triggers/httpreq/invoke?api-version=2022-05-01 return 401 Unauthorized

What type of Logic App Is this happening in?

Standard (Portal)

Which operating system are you using?

Windows

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "httpok": {
                "type": "Response",
                "kind": "Http",
                "inputs": {
                    "statusCode": 200
                },
                "runAfter": {}
            }
        },
        "contentVersion": "1.0.0.0",
        "outputs": {},
        "triggers": {
            "httpreq": {
                "type": "Request",
                "kind": "Http"
            }
        }
    },
    "kind": "Stateless"
}

Screenshots or Videos

No response

Browser

Edge

Additional context

No response