Hi again Alexandre! Just wanted to check again if you have any answer to the two questions above (http.sys changes in newer IW versions + TLS support in different windows versions)?
Also, I have another question now after doing some more successful tests. I have been able to share certificate/port for all 6 applications now in a test setup. If I can successfully make this production ready, I would need to support both old and new urls during a transition period. For example, I would like https://m.mydomain.com/ to be redirected to https://mydomain.com/m/ (or more generally stated: the old url should work in the same way as if I had entered the new url). I cannot easily do this with DNS http redirect records as it will cause certificate warnings when passing DNS servers. Instead, could I point the DNS record for m.mydomain.com to the same (shared) IP all my applications now are using, and redirect it from my main IntraWeb application to one of the other five applications based on the url used to access it? If so, what is the preferred way to do this? Any code examples? Can you make this work also when there are url parameters involved?
Furthermore, besides the two IW application that now would use a non-empty BaseUrl, could I make this redirect work also for the non-IW applications (e.g. redirecting https://api.mydomain.com/ to https://mydomain.com/api/) in the same way? Or are some adjustments needed in those cases?
And finally of course, if you suggest a totally different approach for solving this issue, please say so!
Best regards
Magnus Oskarsson
Also, I have another question now after doing some more successful tests. I have been able to share certificate/port for all 6 applications now in a test setup. If I can successfully make this production ready, I would need to support both old and new urls during a transition period. For example, I would like https://m.mydomain.com/ to be redirected to https://mydomain.com/m/ (or more generally stated: the old url should work in the same way as if I had entered the new url). I cannot easily do this with DNS http redirect records as it will cause certificate warnings when passing DNS servers. Instead, could I point the DNS record for m.mydomain.com to the same (shared) IP all my applications now are using, and redirect it from my main IntraWeb application to one of the other five applications based on the url used to access it? If so, what is the preferred way to do this? Any code examples? Can you make this work also when there are url parameters involved?
Furthermore, besides the two IW application that now would use a non-empty BaseUrl, could I make this redirect work also for the non-IW applications (e.g. redirecting https://api.mydomain.com/ to https://mydomain.com/api/) in the same way? Or are some adjustments needed in those cases?
And finally of course, if you suggest a totally different approach for solving this issue, please say so!
Best regards
Magnus Oskarsson