-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double encoded URLs #920
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you follow the issue template or I may not respond. |
Happy to take a look at the changes. I’m curious why it would only double encode when you build from source but not in the version I release to play store. |
Please take a look at #921 . I truly have no idea why it double encodes only my compilations, but it's bit frustrating. I hope my changes doesn't broke anything. |
Thanks. I am a little confused. In the logs you posted:
Which part is double encoded? It adds an encoding for a space ( |
Oh Interesting, I see |
There are two parts in this problem, simply changing spaces to + signs in URL should be unharmful for everyone, but changes committed to www/js/app.js may provide some troubles. I can remove changes from app.js if you prefer? |
I think I know what is going on. Does that work? |
It seems to me I need to: |
Oh, I can test encodeURIComponent but as of second part it seems to be more complicated than simple function replacement. |
My URI encode is working correctly. I added a logging statement in app.js before encodeURI. This is the URL that is passed:
This is the output of encodeURI:
|
Okay, let's do a quick test. I think its related to the fact that your encoding may not be UTF8 Open up a chrome browser, and its console log (Inspect source - it will give you a console tab) Now do this:
Then please give me the output of:
and then
|
Sorry for slow responses, but I made few tests: New Android app
and test you asked for:
Or should I use true token? |
I'm confused. In your latest log you say:
But in your first post, the encoding is wrong
They both use the same encoding command |
maybe I cutted it to much, here is more of it:
|
ref to investigate more silkimen/cordova-plugin-advanced-http#195 |
@fri-K can you please pull my dev branch https://github.com/pliablepixels/zmNinja/tree/dev and test? |
I'll bet you're surprised, zmNinja 1.4.3 fixes this bug. Well done, thanks :) |
sounds good |
The version of zmNinja you are reporting:
The version and OS of ZoneMinder you are using:
Platform zmNinja is running on
Describe the bug
zmNinja is double encoding URLs when I'm using compiled by myself version (build with build_android.sh script to be exact)
Debug logs
Additional context
I made necessary changes to fix this up, but I'm not sure
I'll create merge request with those changes.
The text was updated successfully, but these errors were encountered: