Proxy liquid downloading file

However you do need to be able to edit configuration files yourself. To do that, you can launch Notepad by "Run as Administrator" command and open web. Expand your server's node.

Create new Application Pool. Make sure you've specified. Net Framework version 4. Specify physical path. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. App Proxy downloading file instead of rendering liquid Ask Question. Asked 2 years, 6 months ago. Active 2 years, 6 months ago.

Viewed times. I'm using laravel-shopify from this repository I have setup correctly app proxy in shopify but problem is that always download the proxy file I host my project in a Digital Ocean Server Any idea, thanks a lot! Replies 7 7. Re: App Proxy downloading file instead of rendering liquid. Specifically, it looked like: Redirect Trailing Slashes Shopify Staff Retired.

Thanks for posting your solution here in the forums for others :. New Member. Hi Charlotte, I'm having the same issue with my file being served for download instead of rendering the liquid code.

Hey OneMangaTwoManga, I know this reply is very late, but I recently encountered this issue when attempting to set up my app hosted on Heroku. Clearing your cache may also work. Important Links.

Recommended for You. By RosalieL Mar 24, Top Contributors. User RANK. View all. Community Browser. Shopify Community. HSTS is a function that tells client that until a specified timeout you are only permitted to connect to this server using https. The recommended timeout and the timeout that LiquidFiles uses is 2 years. Similarly to the session cookie secure flag, LiquidFiles cannot tell clients to force connections over https unless you configure LiquidFiles with the protocol setting to "Force https".

Our experience is that most reverse proxies are not configured for optimum security and have less secure default configuration that what LiquidFiles has. With the default configuration on both, security and performance will therefore be better by not using a reverse proxy. If you implement a Web Application Firewall, take the time to both configure it properly and have a system for ongoing monitoring, you'll block attacks before the reach the web application, get an incrased visibility of the threats and overall increased security.

But with a simple reverse proxy that don't inspect the traffic, the best you can really hope for is that you don't make things worse. NET application uses Windows Integrated authentication mechanism. Once Windows Authentication proxy knows identity of incoming request, it will pull out email corresponding to that Windows user. Therefore, user does not have to be in Intranet zone connected to IIS module and domain controller all the time.

Therefore, if you make LiquidFiles available from both within corporate network and outside corporate network, and users have laptop computers, it is necessary to only authenticate for the first time from within corporate network; after API key has been obtained and stored at laptop computer, it will be possible to use it without connection to LiquidFiles authentication proxy.

You do not need to use Kerberos, though with Kerberos it will work a little bit faster during initial authentication, but the effect is marginal. There's no automated upgrades between versions.