: How to have website (on IIS) return code 503 yet still provide local development How could I have my website running on IIS return the HTTP Header Code of 503 to the public, and at the same
How could I have my website running on IIS return the HTTP Header Code of 503 to the public, and at the same time be able to allow developer to continue developing it locally?
For example, if I use app_offline.htm, it will yield the 503 error to ALL (including the developers), but how could the developer have access and test on it?
Could we make app_offline.htm to be accessible to only a group a people? Or is there any other alternatives to have 503 and local development happen at the same time?
More posts by @Angie530
1 Comments
Sorted by latest first Latest Oldest Best
You might want to ask someone to migrate this to Stack Overflow as it's probably a more appropriate venue for questions concerning website development.
However, your developers shouldn't be 'developing' your live (or 'production') site directly; they should be updating another 'development' site instead and then 'deploying' changes, after they've been tested, to your production site (in a nice, easy, automated way). Doing this would completely obviate your desire for a solution to what you've requested.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.