• Resolved lofesa

    (@lofesa)


    Hi
    I′m testing the plugin and I can see that the cookie content is not url-encoded but plain test.
    Some tools we use need the plugin content be url-encoded to work, can this be achieved?
    F.e:
    {"necessary":"yes","marketing":"no","analytics":"yes","preferences":"no","unclassified":"no"}
    must be

    %7B%22necessary%22%3A%22yes%22%2C%22marketing%22%3A%22no%22%2C%22analytics%22%3A%22yes%22%2C%22preferences%22%3A%22no%22%2C%22unclassified%22%3A%22no%22%7D

    Thx in advance

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WPeka

    (@wpeka-club)

    Hi there,

    Thanks for reaching out.

    Currently we don’t have this feature but we will definitely work on the suggestion which you have provided. And it will be added in the upcoming releases soon.

    You will be updated regarding the same.

    Thank you for your patience.

    Regards,
    Team WPeka.

    Thread Starter lofesa

    (@lofesa)

    Hi
    Thanks for your response.
    As per spec cookie-values must NOT contain control chars and these others ( ) < > @ , ; : \ " / [ ] ? = { }. Url-encoding the cookie-value avoid these chars.
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie

    Plugin Author WPeka

    (@wpeka-club)

    Hi there,

    Thank you for your response.

    We will make sure the cookie values are properly encoded. Also, we have started working on this issue and will provide a future release soon.

    Thanks,
    Team WPeka.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cookie encoded content’ is closed to new replies.