Martin Connell
Martin Connell
Okay, I've marked this as a feature request then. It might involve some sexy regex...
No, I don't think the issue has been raised before. I presumed error output would be caught as is. A PR would be welcome if you have the time.
If you have a particular route that you want excluding from being localized by i18n, you can modify the ```i18n.LocalizedApplication.Current.UrlsToExcludeFromProcessing``` property value to do that. An example of doing that...
I've had custom errors turned off on my current site, but have turned them on and after a bit of playing around with the web.config settings managed to get a...
Also for clarification I don't have ```error``` in the ```UrlsToExcludeFromProcessing``` property mentioned earlier.
If a URL that is already localized is being patched on the way out, that is a bug. Are you able to debug it? The method in question is EarlyUrlLocalizer.ProcessOutgoing....
> Does it mean that i18n looks for HREF tags and patch only url inside these tags? Yes.
In case it helps, you can control outgoing (late) URL localization prior to it happening for a request and subject url. E.g. ``` protected void Application_Start() { ... i18n.UrlLocalizer.OutgoingUrlFilters +=...
As a general solution, you can add a querystring to the URLs NOT to be localized and test for that in the i18n.UrlLocalizer.OutgoingUrlFilters delegate. E.g. `\fr\pdf-word?nolocal`
If I understand you correctly, you suggest that the UrlLocalizer code that parses the response in order to extract URLs be modified to test for the presence of URLs in...