This breaks sub-requests in Silex as far as I can tell. The only real solution is to avoid passing these strings from action to action and deal with them in the same action they're generated in. This is going to create some redundant code for the time being.
If we search
chlorophyll
for example we get a very long SMILES string:Which becomes outright monstrous when URL-encoded:
This breaks sub-requests in Silex as far as I can tell. The only real solution is to avoid passing these strings from action to action and deal with them in the same action they're generated in. This is going to create some redundant code for the time being.