# WordPress DiscourseConnect client - expired nonce

**URL:** <https://meta.discourse.org/t/wordpress-discourseconnect-client-expired-nonce/285374>\
**Category:** WordPress\
**Created:** [November 13, 2023, 7:09pm UTC](https://meta.discourse.org/t/wordpress-discourseconnect-client-expired-nonce/285374 "2023-11-13T19:09:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\
**Post date:** [November 14, 2023, 9:20am UTC](https://meta.discourse.org/t/wordpress-discourseconnect-client-expired-nonce/285374/4 "2023-11-14T09:20:05Z")

</div>

Thanks @simon!

> [@simon](#):
>
> The random string triggers WordPress to break the cache

I’m a little unclear as to why this would clear Wordpress’ object cache, as typically adding a random string to a url is used to avoid the browser’s cache. Which query is being cached in Wordpress’ object cache? I’m seeing a non-object-cache reason why that approach might work

> <https://github.com/discourse/wp-discourse/blob/main/lib/sso-client/query-redirect.php#L74>

However if that’s the case we may need a slightly different tweak. But perhaps I’m missing something?

---

_[View the full topic](https://meta.discourse.org/t/wordpress-discourseconnect-client-expired-nonce/285374)._