Closed
Bug 1155222
Opened 10 years ago
Closed 10 years ago
com.s3.amazonaws.com and similar should probably be added
Categories
(Core Graveyard :: Networking: Domain Lists, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: nyuszika7h, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150415030206
Expected results:
Some sites use domains like static.dpaste.com.s3.amazonaws.com. You shouldn't be able to set cookies for com.s3.amazonaws.com. Not sure what's the best way to go about this, whether <all TLDs>.s3.amazonaws.com should be added or not.
Comment 1•10 years ago
|
||
Indeed, this is a rather unfortunate naming scheme for PSL purposes.
Osman: can you tell us about what's going on here, and Amazon's view of how it should be handled in the PSL?
Gerv
We are discussing this internally and will get back to you with a response in a few days.
Sorry for the delay Gerv. We are still determining a move forward. I'll put some pressure on the teams internally.
Flags: needinfo?(osmans)
A minor update on this, S3 will have move forward by 5/21. Sorry again for the delay.
Comment 6•10 years ago
|
||
osman: ping?
Gerv
gerv: pong
I followed up and escalated internally. I apologize for the delay here. It doesn't normally take us this long to respond..
Comment 8•10 years ago
|
||
We are continuing to investigate a resolution to this. Will have un update by 7/16.
Comment 9•10 years ago
|
||
kilo: ping? :-)
Gerv
Updated•10 years ago
|
Flags: needinfo?(kilo)
Comment 10•10 years ago
|
||
Resolving INCOMPLETE due to lack of input from reporter. kilo: once you've worked out what you are doing, PSL issues are now tracked here:
https://github.com/publicsuffix/list/
Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Updated•10 years ago
|
Flags: needinfo?(kilo)
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•