According to the docs the following is new
SES interceptor now by default does URL extension detection via the incoming routed UR
However if I do
/getParks.xml throws an IIS error
/getParks.wddx also throws an IIS error
I am using the .htaccess but I don’t see anything in there that could be causing this.
Unless I am in the dark ages, .htaccess is not supported by IIS. IIS can import .htaccess files (which is bad ass) and save the configuration in your web.xml.
What is happening is that IIS is aware of what an “xml”/“wddx” file is and is trying to serve the actual file.By removing the mime-type associated within IIS you should be able to fix this. Another solution would be to resolve this in your rewrite rules. If you plan on allowing xml files to be downloaded (like your sitemap.xml for search engines) I recommend you resolve this using rewrite rules that only apply to the paths you are trying to serve xml files from via ColdBox–or, allow the rewrite rule to work on all paths except the ones you want actual files delivered through.
Hope that helps.
No you are not in the dark ages so to speak, I use an application from Helicon to do the rewrite, and it uses standard .htaccess files.
Ok, I’ll have to have a look into this further.
Ok, I forgot to I can understand xml in that case. But wddx is not a mime type by default so it should not be a problem either.
Your rewrite rules should solve this.
Sounds good but I am not really an expert on that side of things, so I would not know what to even do there.
Do you have any XML files you need to serve?
If no, it’s super easy… You probobly have a line that looks something like this:
If you do, remove the “xml”. That is the regex that stops URLRewriting (which means your web server is looking for the file).
Hope that helps.