The skip/bypass rule/code works on my testing site and there is nothing else in your Request URI and Query String that could be blocked by BPS. You can try turning off BPS Security Logging and see if you still see a 403 error from your server. BPS logs all 403 errors, but not all 403 errors are necessarily generated by or caused by BPS. Example: BPS definitely was blocking that URI and Query String because it exactly simulates an RFI hacking attempt against your website. So whitelisting that works perfectly using the code above, but if something on your server is also blocking that hacking attempt then a 403 error will still occur. To completely eliminate BPS activate Root folder Default Mode. That turns off Security Logging and creates a default WordPress root .htaccess file without any security code in it. Also you need to clear your plugin cache and your Browser cache to ensure that what you are seeing is current/now and not the past/cached.
On my testing site using the same URL parameters in the URL String you will see a 404 error, NOT a 403 error after whitelisting the hacking attempt string. I assume the 404 error is occurring because the URL is not valid and does not make any sense to me whatsoever since that page cannot exist where the URL is pointing to, but the URL string itself is not being blocked after whitelisting it using the code I posted above.
[link removed – testing example completed]
This Google Translate URL on the other hand does make sense: http://www.google.com/translate_c?langpair=en&u=http://example.com/bpspro/nextgen-gallery-test/