Repository navigation
Conversation
|
You should forward requests from guru3d.com to www.guru3d.com and add a cookie rule. |
|
@J0WI Can you pull? |
|
@Ekaris Please fix your rule to also forward https queries: You're still missing a cookie rule, you should start adding these for complete coverage. Also list the following as refused: |
|
I didn't get any cookies on www.guru3d.com. |
|
Good? |
|
@J0WI you are probably blocking them, I see 5 cookies, all __utm related, originating from Also you have no way of knowing what or who links to this website. There is no downside to forwarding the https domain. @Ekaris sorry you're getting bounced around like this... Note: you've actually removed the redirect entirely. |
|
I only get 1 cookie and it's empty, besides using securecookie on all rules is a theme for a discussion on mailing list, can you pull @J0WI ? |
|
@Ekaris No, it isn't. Setting secure cookie on all rules would be stupid, hence why it's optional. It's to be used on a case by case basis where it doesn't break a website. In this situation the rule is so simple it can be safely used. Also, stop demanding your PRs be merged, ask for review. They will be merged when they are ready, yours isn't. You need to fix your redirect for ^guru3d.com as I already stated. |
|
I agree that this discussion should be somewhere else. I never required to secure cookies in the past and I won't require it here - nevertheless it would be nice to have. But the redirect from ^ to www is a real blocker. |
|
@J0WI Not trying to imply that a securecookie rule should be a requirement. However, as a frequent contributor, it is something he should consider adopting for complete coverage. |
|
Only issue I see is you've accidentally got 4 w's in the cookie host. For future reference, you can just use The test URL shouldn't be needed I don't think ( @J0WI ?). The script should handle it. |
|
Thanks! |
No description provided.