# |
Apr 5th 2019, 10:27 |
asdfgh |
*i have used |
# |
Apr 5th 2019, 10:25 |
asdfgh |
how can i create a custom encrypt key for cookie only ? |
# |
Apr 5th 2019, 10:25 |
asdfgh |
but i cannot change the salt (for the Auth component reason) |
# |
Apr 5th 2019, 10:25 |
asdfgh |
because i encrypt the cookie |
# |
Apr 5th 2019, 10:25 |
asdfgh |
dereuromark last thing...i have using an old security salt...now i get Invalid key for encrypt(), key must be at least 256 bits (32 bytes) long. |
# |
Apr 5th 2019, 10:25 |
asdfgh |
ok |
# |
Apr 5th 2019, 10:23 |
dereuromark |
maybe there is withCookies()? |
# |
Apr 5th 2019, 10:23 |
dereuromark |
check if you can combine them somehow. |
# |
Apr 5th 2019, 10:23 |
asdfgh |
i do not like it too |
# |
Apr 5th 2019, 10:23 |
asdfgh |
? |
# |
Apr 5th 2019, 10:23 |
asdfgh |
dereuromark so basicaly if i have two cookie i must do $this->response = $this->response->withCookie(new Cookie(ONE)) and again $this->response = $this->response->withCookie(new Cookie(TWO)) |
# |
Apr 5th 2019, 10:20 |
dereuromark |
i dont like it either, but thats how the psr people wanted to have request and response |
# |
Apr 5th 2019, 10:20 |
dereuromark |
its called immutability |
# |
Apr 5th 2019, 10:18 |
asdfgh |
?? |
# |
Apr 5th 2019, 10:18 |
asdfgh |
$this->response = $response; |
# |
Apr 5th 2019, 10:18 |
asdfgh |
$response = $this->response->withCookie($cookie); |
# |
Apr 5th 2019, 10:18 |
asdfgh |
is there any sense of doing: |
# |
Apr 5th 2019, 10:16 |
asdfgh |
then should i add that response to the reponse of the controller? |
# |
Apr 5th 2019, 10:15 |
asdfgh |
guys $response = $this->response->withCookie($cookie); |
# |
Apr 5th 2019, 10:08 |
neothermic |
https://book.cakephp.org/2.0/en/core-libraries/caching.html#using-groups however, I suspect this might not affect us as we don't seem to use groups :slightly_smiling_face: |
# |
Apr 5th 2019, 10:08 |
neon1024 |
Perhaps someone forgot to update the documentation? Tracking down the commit would shed some light no doubt |
# |
Apr 5th 2019, 10:08 |
neothermic |
its not even shown in the example configs |
# |
Apr 5th 2019, 10:08 |
neothermic |
it isn't, at all. |
# |
Apr 5th 2019, 10:08 |
neon1024 |
So it wouldn’t appear there |
# |
Apr 5th 2019, 10:07 |
neon1024 |
I always understood it to be in your cache configuration |
# |
Apr 5th 2019, 10:07 |
neothermic |
https://github.com/cakephp/cakephp/blob/2.x/lib/Cake/Console/Templates/skel/Config/core.php is void of the word `group` |
# |
Apr 5th 2019, 10:06 |
neothermic |
@neon1024 that's the fun part, the core.php doesn't even mention the groups option |
# |
Apr 5th 2019, 10:04 |
neon1024 |
Or even just reading the source code |
# |
Apr 5th 2019, 10:04 |
neon1024 |
Writing a key to Memcached isn’t hard, nor is reading they key |
# |
Apr 5th 2019, 10:04 |
neon1024 |
Nor are they more impressive as such |
# |
Apr 5th 2019, 10:04 |
neon1024 |
Things don’t have to be hard |
# |
Apr 5th 2019, 10:03 |
neon1024 |
Then make the problem smaller |
# |
Apr 5th 2019, 10:03 |
neothermic |
it's a bit difficult to replicate ~1GB of live cache :P |
# |
Apr 5th 2019, 10:03 |
neon1024 |
Sounds like you have a requirement for a more fluid and customisable development environment |
# |
Apr 5th 2019, 10:02 |
neothermic |
and on our staging servers the cache lifetime isn't long enough to get a concrete answer :P |
# |
Apr 5th 2019, 10:02 |
neothermic |
@neon1024 it'd be irresponsible to TIAS on our production servers :P |
# |
Apr 5th 2019, 10:01 |
slackebot2 |
!tias |
# |
Apr 5th 2019, 10:01 |
slackebot2 |
Command sent from Slack by neon1024: |
# |
Apr 5th 2019, 10:01 |
neon1024 |
So, no? |
# |
Apr 5th 2019, 10:01 |
neon1024 |
> Cache keys used for groups are now hashed |
# |
Apr 5th 2019, 09:54 |
neothermic |
Hmm, question WRT going through 2.10.7: ```Cache keys used for groups are now hashed. This prevents keys overflowing Redis and Memcache key lengths. This will cause previously cached entries to be invalid as group keys have changed.``` If we don't use groups, will this still affect our keys? |