Skip to content
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

Don't use cookies in send2cgeo #12

Open
Lineflyer opened this issue Jun 26, 2015 · 3 comments
Open

Don't use cookies in send2cgeo #12

Lineflyer opened this issue Jun 26, 2015 · 3 comments

Comments

@Lineflyer
Copy link
Member

From @Lineflyer on August 9, 2012 19:30

From support mail:

For the send2cgeo – Userscript it is necessary to accept cookies. If the cookies are deleted (so in my case) I have to reconnect/reregistrate my browser and phone on your homepage before I use the script on the GC-homepage. The Greasemonkey-Project allows you to store some data in the browser (also after restart), so that you don’t need cookies!

Copied from original issue: cgeo/cgeo#1946

@Lineflyer
Copy link
Member Author

From @jeancaffou on August 9, 2012 23:22

I vote for passing the unique token / ID via GET.
It's as secure as sending the ID/token via cookie.

This method is more permanent and useful for scripting and also greasemonkey script can be generated dynamically so that it would include the token.

@Lineflyer
Copy link
Member Author

From @BudBundi on August 15, 2012 8:25

We can save a value via http://wiki.greasespot.net/GM_setValue
and get so send http://wiki.greasespot.net/GM_getValue but than must the code on HP change.
Perhaps for both methods cookie and setting over script.

@Lineflyer
Copy link
Member Author

From @jeancaffou on August 15, 2012 8:27

But please do not drop the cookie functionality if you decide to change the greasemonkey script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant