[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-167: -- Fix Version/s: (was: UserALE.js 1.0.0) UserALE.js 1.1.0 > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: Website 0.1 >Reporter: Rob Foley >Assignee: Alex Ford >Priority: Major > Fix For: UserALE.js 1.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-167: -- Request participants: (was: ) Remaining Estimate: 2h Original Estimate: 2h > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.3.0 >Reporter: Rob Foley >Assignee: Alex Ford > Original Estimate: 2h > Remaining Estimate: 2h > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-167: -- Sprint: Sprint 7 > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.3.0 >Reporter: Rob Foley >Assignee: Alex Ford > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-167: -- Sprint: (was: Sprint 6) > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.4 >Reporter: Rob Foley >Assignee: Joshua Poore > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-167: -- Sprint: Sprint 6 > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.4 >Reporter: Rob Foley >Assignee: Joshua Poore > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Foley updated SENSSOFT-167: --- Reporter: Rob Foley (was: Chris Muto) > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.4 >Reporter: Rob Foley >Assignee: Rob Foley > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENSSOFT-167) Browser plugin CORS permissions
[ https://issues.apache.org/jira/browse/SENSSOFT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Muto updated SENSSOFT-167: Request participants: (was: ) [~rf] I'm not sure why this auto-assigned to you, but I am looking into this. I don't seem to have permission to update asignee > Browser plugin CORS permissions > --- > > Key: SENSSOFT-167 > URL: https://issues.apache.org/jira/browse/SENSSOFT-167 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.4 >Reporter: Chris Muto >Assignee: Rob Foley > > Firefox and Chrome both have security features that disallow cross-origin > logging (e.g. logging information to sitea.com from a javascript function on > siteb.com). Since our plugin will need to log to a fixed url no matter what > url the user is on, we'll need to bypass this security feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
