ODataExceptions in DefaultODataPathHandler mean that the incoming request is incorrect or not supported. These should result in 404 or 400 rather than a 500.
For now, a workaround would be to have a custom path handler that looks like this,
```
public class CustomPathHandler : DefaultODataPathHandler
{
public override ODataPath Parse(IEdmModel model, string odataPath)
{
try
{
return base.Parse(model, odataPath);
}
catch (ODataException e)
{
return null;
}
}
}
```
For now, a workaround would be to have a custom path handler that looks like this,
```
public class CustomPathHandler : DefaultODataPathHandler
{
public override ODataPath Parse(IEdmModel model, string odataPath)
{
try
{
return base.Parse(model, odataPath);
}
catch (ODataException e)
{
return null;
}
}
}
```