Error in Kudu when executing sailsdeploy.ps1

[szelee]

Hi,

I am getting this following error in Kudu, which result the command prompt continue to display "computing?" in the long list.

A potentially dangerous Request.Path value was detected from the client (:). at System.Web.HttpRequest.ValidateInputIfRequiredByConfig() at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context) https://sails-app.scm.azurewebsites.net:443/api/triggeredwebjobs/E:/projects/testProject/node_modules/sails-deploy-azure/payload/sailsdeploy.ps1 /api/triggeredwebjobs/E:/projects/testProject/node_modules/sails-deploy-azure/payload/sailsdeploy.ps1

Please assist me on this matter. Thank you,
Szelee

[megakoresh]

Same, bumping this.

[UPDATE]: Ok so I am not exactly sure I am having the same issue (the result is still the same on sails deploy command though). When I do azure site log tail the following is outputted after upload is done:

2015-09-30T06:51:37  Welcome, you are now connected to log-streaming service.
2015-09-30T06:51:45    Outgoing response, type: response, statusCode: 412, statusText: Precondition Failed, Server: Microsoft-IIS/8.0, x-ms-request-id: b6395909-3c94-4a7d-8f55-c01f1e4f691e, ETag: "02633d4962c9d208", Cache-Control: private, X-AspNet-Version: 4.0.30319, Content-Type: application/json; charset=utf-8
2015-09-30T06:51:47    Outgoing response, type: response, statusCode: 412, statusText: Precondition Failed, Server: Microsoft-IIS/8.0, x-ms-request-id: 22ec1960-9e9b-45f6-b162-c30d6f28e21e, ETag: "02633d4962c9d208", Cache-Control: private, X-AspNet-Version: 4.0.30319, Content-Type: application/json; charset=utf-8
2015-09-30T06:51:48    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: ebb9a029-1f8e-4597-b0f9-8208fd2b46d5, Cache-Control: private, X-AspNet-Version: 4.0.30319, Content-Type: application/json; charset=utf-8
2015-09-30T06:51:48    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: d5d5d213-746f-4184-bf0c-b04a972e2237, Cache-Control: private, X-AspNet-Version: 4.0.30319, Content-Type: application/json; charset=utf-8
2015-09-30T06:51:49    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: 2022d866-c3e6-4316-a0a0-90c9480f5751, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:50    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: 18a3abcb-887a-4468-937e-c9aa09293da9, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:52    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: 14ac98e8-e833-4497-bb0c-1df6ca1573dc, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:53    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: 246d2d65-4aec-48ce-837c-c140888a5fbd, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:54    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: f81e827d-c2fa-45d7-9ea5-734f2aaf144a, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:56    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: 7cc60a2a-7e7c-4215-a1eb-f837d2255178, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:57    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: a1122e23-5ef0-4544-a65c-a697249a4948, Cache-Control: private, X-AspNet-Version: 4.0.30319
2015-09-30T06:51:58    Outgoing response, type: response, statusCode: 404, statusText: Not Found, Server: Microsoft-IIS/8.0, x-ms-request-id: 69a965ed-ad44-4677-96e2-608b73031602, Cache-Control: private, X-AspNet-Version: 4.0.30319

As soon as the 404 responses start the script says Failed to fetch script status.

[megakoresh]

Ok fixed it. This has to do with Windows path format. That was a &/"#((" pain to figure out...
The bug resides in machinepack-azure\machines\upload-webjob.js
Job name formatting uses / for path resolution, whereas in Windows is \. I think it's too trivial a fix for me to clone the repo and so on, so here's a pic of the fixed file. Whoever has the repo, it's a 2 second edit... And I am sure it'll save dozens of people a LOT of headache.

That still doesn't fix all the issues like 260 character limit and compliation errors etc. etc. that Azure has, being a terrible node.js host, but that's a different matter. Cheers!

[felixrieseberg]

Awesome job figuring it out. Just for reference: The latest version on GitHub now has the fix (and should work). Until @mikermcneil publishes to npm, simply install directly from GitHub:

{
"dependencies": {
    "sails-deploy-azure": "mikermcneil/sails-deploy-azure#0f3ea43c60ed2149d3e292fa4472e668c33cbd24"
  }
}