Title: ianap's Replies | WordPress.org

---

# ianap

  [  ](https://wordpress.org/support/users/ianap/)

 *   [Profile](https://wordpress.org/support/users/ianap/)
 *   [Topics Started](https://wordpress.org/support/users/ianap/topics/)
 *   [Replies Created](https://wordpress.org/support/users/ianap/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/ianap/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/ianap/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/ianap/engagements/)
 *   [Favorites](https://wordpress.org/support/users/ianap/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Pressidium Cookie Consent] Cookie scan help](https://wordpress.org/support/topic/cookie-scan-help/)
 *  [ianap](https://wordpress.org/support/users/ianap/)
 * (@ianap)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/cookie-scan-help/#post-17553781)
 * There is no way to “scan” the cookies your application might set to clients. 
   Imagine a situation where your application sets 2 cookies for visitors from US
   while the scanning tool runs from Europe, or a cookie that is set when an order
   is made. You need to either *know* the full codebase and what might be set based
   on different criteria, or write code to record all your responses with `set-cookie`
   involved to identify the cookies you might set.
 * No external “cookie scanning” tool can ever be 100% correct.

Viewing 1 replies (of 1 total)