|
| Question: | I tried everything. If I manually add the shorty-id to my configured static backend, it works perfect. But if I try to validate via the global ownCloud settings it throws an error: Verification failed!
How can I force shorty to set my static backend?
Thanks!
| |
| | Answer: | Thanks for that question...
indeed you address one unconvenient issue in the app:
I tried hard to get the validation strategy for configuring the 'Static Backend' working in all situations. Currently to my knowledge that validation works correct in all situations, also for cross domain setups for ownCloud in version 4.0 and 4.5. There is only one (known) exception: validation attempts of http based static backends validated from inside an ownCloud addressed via https will fail although the setup is correct and usable (false negative). This is the result of security guidelines inside the browser implementations.
Note however that although that validation fails in those special setups the backend configuration is still usable, provided the configuration is correct and requests are actually mapped back to the Shorty app. A positive vaidation of a backend configuration is not required to use that backend. At runtime Shorty does simply string operations when using that backend. So if in doubt give it a try: despite the negative validation, if you are really sure the configuration should work, just generate a Shorty and have a try resolving it. Chances are your setup is perfectly usable regardless of the negative validation. You Shorty should be resolved, your browser be redirected to the final target and the click should be registered. So the number of clicks in the Shorty should be incremented, if you have the additional Tracking plugin installed you should be able to see the requests details inside the list of clicks.
Sorry for those inconveniences, such cross domain requests are really hard to implement in todays security aware times...
For ownCloud version 5 things will change, the current validation strategy will stop working for any cross domain situation. So I have to find a solution for this issue anyway. From version 0.3.19 on Shorty is usable inside the (upcoming) ownCloud version 5, though it will still stay backward compatible for any version 4.0 or 4.5 based installations.
If my current idea works out it will provide a clean solution for both aspects: cross domain and cross protocol validations. This solution, if working, will be part of a future release which then once and for all solves this issue for all supported ownCloud versions: 4.0, 4.5 and 5.x
So another step towards world domination ;-)
** UPDATE **:
I just released version 0.3.26 of the Shorty app.
Amongst other changes that update contains a new strategy of the validation dialog. It currently looks like this strategy complies with the security changes introduced with version OC5. So it is possible to verify the base url as required to setup a Static Backend again! Hurray!
Edit answer | |
|
Back to overview
Add comment
|
