How do I force Azure Apps to use latest html file? - html

I have a web application hosted on azure apps that I publish using visual studio. It is a flask app. One of the templates is called searchresult.html. I am making changes to this file that are made when I run locally. When I run it on the server though the changes are absent.
Using the azure console I can see that the changes are present in the file that is stored on the server, but the application continues to deliver the old html.
How can I force azure to see my updated file?
Things I have tried:
Deleting the file directly on the server and re-publishing it
Committing changes to git, even though I knew that would do nothing
Testing it locally (it works)
Restarting the application

Since you said you already check the file has been changed on the Kudu, so it supposed not an issue of deployment. You could disable caching in your browser.
such as in chrome browser, navigate to F11 window and select the Disable cache blanket.
or please try to access your website via incognito model.
In addition, I crashed into similar issue with you in other web app. My previous solution is that enable always on option on the portal and restart my app, it worked.
Just for your reference.Hope it helps you.

Related

Is there a way to overwrite local files in Google Chrome with service worker running?

Just found that if you have a service worker in your app and you use local overwrite in Chrome dev tools, the view shows a new file but it executes the old file, so you can't use the debugger properly. But anyway it doesn't work at all the file is not updated.
My service worker is only to allow using files in memory (from indexedDB) and the rest of the files just use fetch in Worker (no cache).
I was also trying to use extension resource overwrite but it also doesn't work.
Does anyone know how to change the file locally without modifying an app where the service worker is running?
I'm not sure If I should report this to the Chrome Dev tools team, since this is like a bug or missing an important feature.Just found that if you have a service worker in your app and you use local overwrite in Chrome dev tools, the view shows a new file but it executes the old file, so you can't use the debugger properly. But anyway it doesn't work at all the file is not updated.
My service worker is only to allow using files in memory (from indexedDB) and the rest of the files just use fetch in Worker (no cache).
I was also trying to use extension resource overwrite but it also doesn't work.
Does anyone know how to change the file locally without modifying an app where the service worker is running?
I'm not sure If I should report this to the Chrome Dev tools team, since this is like a bug or missing an important feature.

Automatically refresh browser on save

Is there a way to have the chrome browser automatically refresh whenever the file it's accessing changes? I want to run my files locally (not with a server). I'm using atom. I've so far found "browser-refresh-on-save" as an atom package but it does not work on Windows 32, which is what I'm using. All other solutions I've found require me to be running a server.

Headless Chrome fails under IIS but works on command line

I am wrapping headless chrome using the excellent ChromeHtmlToPDF library. This we are using to dynamically render PDFs from a website. This works locally under IIS express, and also works on the server when recompiled as a console app, so the technology works. However running under IIS, chrome always exits immediately and a error of "one or more parameters are invalid", is returned.
You can fix this by passing Chrome a custom user profile directory:
chrome.exe --user-data-dir="C:\NewChromeProfile" ...
This directory will be created by the account under which Chrome is running, and therefore the account will have the permissions it needs.
After many many hours looking into this I finally solved it by running it under my own user, the restricted IIS user, then comparing the activity logs generated by the excellent microsoft process monitor.
I tracked it down to file permissions on one directory: C:\Windows\System32\config\systemprofile\AppData\Local\Google\Chrome\User Data
The app pool user needs write + modify permissions to this directory. It's up to you if you feel this is an acceptable security risk; however for us it is, for now.
This is where headless chrome stores it's crashpad directory. No amount of parameter fiddling seems to be able to dissuade it of this. That seems to be a bug.
Hope this helps someone else, I couldn't find anything on this anywhere.

How to use live edit with router script in PhpStorm

I setup live edit in PhpStorm and it works great. While implementing routing in my application, I configured PhpStorm to use a routing script using the Built-in Web Server run configuration. At this point, live edit stopped working because it seems to work only with the built-in webserver and not the PHP built-in web server. (Technically, it didn't stop working, rather there were two run configurations: live edit where the links returned a 404 and a routing configuration that doesn't have live edit.)
Is it possible to use both live edit and a routing script?
Does anyone have any workarounds to using live edit or similar functionality when working on an app that uses routing? I currently have a keymap (Alt-R) setup for Reload in Browser.
I'm using PhpStorm 10.0.2 (PhpStorm-143.790) on CentOS 7.
Note: I found two issues relating to live edit and routing but neither was helpful.
https://youtrack.jetbrains.com/issue/WEB-15762
https://youtrack.jetbrains.com/issue/WI-20824
Thanks
A hint in the 2nd URL above provided a suitable workaround. The key lies in the fact the link between the browser and PhpStorm is not tied to the URL; only the tab. To make this work, you need two run configurations:
A JavaScript Debug configuration for live edit. Make sure live edit is working.
A PHP Built-in Web Server configuration with the router script enabled.
Run the JavaScript Debug configuration and it will open a tab in Chrome linked to PhpStorm. Then start the PHP Built-in Web Server configuration and change the "live edit" tab to the URL for the built-in web server. Any changes will automatically refresh the tab using the PHP Built-in Web Server configuration which contains the router functionality.
This concept can also be applied to any functionality not supported by the built-in web server, like SSL. You just need a 2nd web server (built-in or external) and change the live edit tab to the 2nd URL.

Why does the asp.net website administration tool give timeout message (mysql db)?

i have an asp.net-mvc website and I am trying to use the asp.net website administration tool but when i click in visual studio 2010 to launch it, it brings up a browser that says:
An error was encountered. Please return to the previous page and try again.
i can't click back but when i click on "How do i use this tool", i get this error:
Tool Has Timed Out
As a security measure, the Web Site Administration Tool times out after a period of inactivity. Changes to machine.config or web.config may also result in the tool needing to be restarted. To continue configuring your web site, restart the tool.
when i run my website, i am able to connect to the database fine and i am also able to insert new users through the default Account/LogOn interface.
Any suggestions on how to debug why i can't launch the admin tool ?
The project's path shouldn't contain #% or spaces
Could you please try the following:
Close your browser completely. Whether you are using IE or Firefox to test your website, you should make sure all browser windows are closed.
Kill the asp.net development server. It is located in your taskbar
Or, if you are hosting your site in IIS, force an iisreset.
Now try to run the Web Site Administration Tool again.
If it still does not work yet, could you please provide which browser you are using, and which OS and host?
The project's path shouldn't contain #% or spaces
My Project path was D:\Programming\C#\Tests\MVCApplication\
and that is what caused the problem.
I was getting the exact same error message with VS2010 .NET 4.0 framework. I created my solution in a subfolder titled "C#". Renaming the subfolder to CSharp fixed my problem.
I hope this helps.