reverse proxy problem "WARN RESTFilter - Error in REST API"

[dsm1212]

I've had a reverse proxy set up forever on my NAS and when I updated the software on the NAS, API clients stopped working (iphone/android). Browser is fine. The problem is something to do with the reverse proxy because if I connect the app to subsonic directly it works. Here's all I've got for the reverse proxy:

ProxyRequests Off
ProxyPreserveHost Off

<Location /subsonic/>
ProxyPass http://192.168.1.200:4040/subsonic/
ProxyPassReverse http://192.168.1.200:4040/subsonic/
Allow from all
</Location>

I have the root of subsonic set to /subsonic.

I assume this broke due to some change in apache or its configuration. I appear to be running a 2.2.29-netgear2 build. I'm not sure what version it was before.

The errors in the log look like this below. The error happens when I try to open an artist to list the albums. Any suggestions what to check in my apache config???

steve

[2014-12-21 10:56:33,617] WARN RESTFilter - Error in REST API: Access denied to file Adele
java.lang.SecurityException: Access denied to file Adele
at net.sourceforge.subsonic.service.MediaFileService.getMediaFile(MediaFileService.java:151
)
at net.sourceforge.subsonic.controller.RESTController.getMusicDirectory(RESTController.java
:489)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.web.servlet.mvc.multiaction.MultiActionController.invokeNamedMethod(
MultiActionController.java:473)
at org.springframework.web.servlet.mvc.multiaction.MultiActionController.handleRequestInter
nal(MultiActionController.java:410)
at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.
java:153)
.
.
.

[dsm1212]

Very strange, but this appears to have been something strange with subsonic. After running the "clean database" option it cleared up. Odd that this only affected the REST API clients.

steve

[Exrace]

Maybe url formats?