{"action":"closed","issue":{"url":"https://api.github.com/repos/aramrami/OWASP-CSRFGuard/issues/7","labels_url":"https://api.github.com/repos/aramrami/OWASP-CSRFGuard/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/aramrami/OWASP-CSRFGuard/issues/7/comments","events_url":"https://api.github.com/repos/aramrami/OWASP-CSRFGuard/issues/7/events","html_url":"https://github.com/aramrami/OWASP-CSRFGuard/issues/7","id":55282275,"number":7,"title":"some small issues in csrfguard-test","user":{"login":"ccronemberger","id":1625508,"avatar_url":"https://avatars.githubusercontent.com/u/1625508?v=3","gravatar_id":"","url":"https://api.github.com/users/ccronemberger","html_url":"https://github.com/ccronemberger","followers_url":"https://api.github.com/users/ccronemberger/followers","following_url":"https://api.github.com/users/ccronemberger/following{/other_user}","gists_url":"https://api.github.com/users/ccronemberger/gists{/gist_id}","starred_url":"https://api.github.com/users/ccronemberger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ccronemberger/subscriptions","organizations_url":"https://api.github.com/users/ccronemberger/orgs","repos_url":"https://api.github.com/users/ccronemberger/repos","events_url":"https://api.github.com/users/ccronemberger/events{/privacy}","received_events_url":"https://api.github.com/users/ccronemberger/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-23T13:41:21Z","updated_at":"2015-12-17T17:04:46Z","closed_at":"2015-12-17T17:04:46Z","body":"While running csrfguard-test I have found a few problems. I intend to work on them after the release of the project I am currently working on, which is supposed to be next week.\r\n\r\n1 - the browser is caching the html requests (we could play with the http headers to fix this, but maybe it is better to create a servlet to replace the protect.html)\r\n2 - in ajax.html in the ajax method, the checking of whether the csrf check worked or not is wrong: it was reporting \"200: passed csrf check\" even when the served page was error.html\r\n3 - links to \"http://localhost/test.html\" do not work when running on port 8000 which is configured in the pom.xml\r\n\r\n "}}