We have an middleware which generates a URL to download some files based on different type of request it receives. Now our middleware is deployed on windows environment. So while generating the url for appending the file path we are using the operating System's default path separator. For windows the default file path seprator is / i.e. backslash. If you want to know why file seprator for windows is / I have a nice blog for you here here.
So the url which gets generated usually looks likes the below url.
https://test.com:9000/elearning/filedownload?file-path=bulk\AssembledBDEFile1_1455748875242.xml
you can observer that after bulk keyword backslash are started because of the default file path separator.
This middleware is used by different third party applications. The problem is that the third party's are not accepting this url's they are saying, All of the communication is happening over web protocols so only forward slashes should be present and throwing an exception on use of \ . We are using OS default file separator because we want to make our middleware platform dependent.
We asked them to accept the url with combination of / and \ but they are not accepting our request saying \ are not part of web protocol.
So I just want to to know Is using \ is against web protocols and we are doing it in wrong way. Means we have to chnage our middleware or we should force themm to chnage their code.
Can anybody explain the role of \ in web protocols???