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

API key issues #16

Open
andydust opened this issue Jan 7, 2013 · 0 comments
Open

API key issues #16

andydust opened this issue Jan 7, 2013 · 0 comments

Comments

@andydust
Copy link

andydust commented Jan 7, 2013

Tested in Chrome on OSX.

It appears that after the initial api request, for subsequent requests the value of the api key param is null. For example, I can successfully pull down a list of tasks ( in this instance I believe the apikey is read directly from the form input value ), but then when I try to immediately edit the time taken for a task, my php debugging indicates that the api key is null.

Refreshing the page fixes the issue, which leads me to believe that although the cookie value for the api key is set, it cannot be read back until a full browser refresh has occured. This may be browser specific behaviour.

Perhaps this could be solved by creating a reference cache to the api key the first time it is read (whether via the input form or cookie) , and only reading from the cookie if the reference is undefined, like a memoization.

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

No branches or pull requests

1 participant