View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002501 | GNUnet | GNS | public | 2012-07-17 22:04 | 2012-11-05 18:34 |
| Reporter | schanzen | Assigned To | schanzen | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.4 | ||||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0002501: GNS proxy same origin policy and CORS | ||||
| Description | Atm the proxy tries to rewrite all links using the LEHO in the HTML to the GNS name so that js et al are not blocked by the browsers SOP. Of course for example url's generated by js or something alike can't be rewritten like that. Maybe CORS is a saner approach to this issue: http://en.wikipedia.org/wiki/Cross-origin_resource_sharing For example: Maybe it makes sense to add the domain=<LEHO> part given from the webserver as CORS header to the browser AND replacing it with the GNS name in the cookie. Another less GNSssy way is probably to ONLY add the GNS name to the CORS header and leaving the cookie domain intact/send a second cookie with the GNS name. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-07-17 22:04 | schanzen | New Issue | |
| 2012-07-17 22:04 | schanzen | Status | new => assigned |
| 2012-07-17 22:04 | schanzen | Assigned To | => schanzen |
| 2012-08-03 22:52 | schanzen | Note Added: 0006270 | |
| 2012-08-03 22:52 | schanzen | Status | assigned => resolved |
| 2012-08-03 22:52 | schanzen | Resolution | open => fixed |
| 2012-08-03 22:52 | schanzen | Product Version | => 0.9.4 |
| 2012-08-03 22:52 | schanzen | Fixed in Version | => 0.9.4 |
| 2012-08-03 22:52 | schanzen | Target Version | => 0.9.4 |
| 2012-11-05 18:34 | Christian Grothoff | Status | resolved => closed |
