azure-web-sites

I am attempting to host multiple websites in a single Azure WebApp rather than having multiple web apps each hosting a site. Each of these sites is rather small, but in order to meet the requirements of the SLA with Azure, we need to have the server scaled with more than one instance for our Production environment, thus the reasoning for combining sites. After researching this topic, I have got the following setup with our Azure account. Created the proper CNAME DNS records in our zone manager (complete and works). Setup the Azure WebApp to respond to the subdomains (complete and works). Setup

I am running an ASP.NET 5 project in an Azure Web App. When calling on an API endpoint with a file (form-data) of about 1.5mb or larger, the following exception is thrown. Here is where the exception is thrown from . Does anyone know how this can be fixed? Is there a possible workaround? System.IO.InvalidDataException: Unexpected end of request content at Microsoft.AspNet.Server.Kestrel.Http.MessageBody.ForContentLength.d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at

I have an azure website setup in West-Europe and in Standard mode. Suddenly today at 30 January 2014 03:00 am UTC it started constantly restart the app pool. The ShutdownReason is HostingEnvironment. I have a lot of these events in eventlog.xml: <Event> <System> <Provider Name="W3SVC-WP"/> <EventID>2299</EventID> <Level>3</Level> <Task>0</Task> <Keywords>Keywords</Keywords> <TimeCreated SystemTime="9:14:50 AM"/> <EventRecordID>15807234</EventRecordID> <Channel>Application</Channel> <Computer>RD00155D3A08C6</Computer> <Security/> </System> <EventData> <Data>Worker Process requested recycle due

I'm troubleshooting performance / scalability issues with an asp.net app we've migrated to asp.net core 2.0. Our app is hosted on azure as an app service, and is falling over far too easily with any moderate traffic. One thing that's puzzling me is how multiple concurrent requests are handled. From what I've read here , Kestrel uses multiple event loops to handle your requests. But the actual user code is handled on the .net thread pool ( that's from here ). So, as an experiment - I've created a new asp.net core 2.0 MVC app, and added a rather nasty action method: [AllowAnonymous] public

I'm using a Webjob with the Windows Azure Storage SDK. When a new item shows up in a Queue, a method in my class is invoked. According to the SDK docs , if I take a TextWriter as a parameter to my method, the SDK will provide me with a TextWriter that I can write to which will show up in the Webjob's logging infrastructure. This makes it pretty easy to diagnose issues and troubleshoot things. public async static void ProcessQueueMessage([QueueTrigger("queueName")]MyModelType model, TextWriter logger) { await logger.WriteLineAsync(string.Format("Processing Item {0}", model.SasUrl)); // Some

I know there are some similar questions like so unexpected token after angular 2 production build but it doesnt actually answer my question. Basically I have an angular app and its a PWA, now everytime I do a new production build the first time I visit the site I get an error like so and then as soon as I refresh the page, the site works as normal. This happens on any browser/device Now my suspicion is that every time the app is updated, the main bundled js file changes, and the PWA has cached the old one and the app is still trying to use the new one. My Project structure is as follows I have

I have an Azure Web App that I want to use to screen scrape a website when I call an Action on a controller, like so. var driver = new PhantomJSDriver(); driver.Url = "http://url.com"; driver.Navigate(); var source = driver.PageSource; var pathElement = driver.FindElementByXPath("//table[@class='someclassname']"); string innerHtml = ""; IJavaScriptExecutor js = driver as IJavaScriptExecutor; if (js != null) { innerHtml = (string)js.ExecuteScript("return arguments[0].innerHTML;", pathElement); } return innerHtml; This works fine locally, however when I upload to my Azure Web App, I get this