Modify ↓
Opened 15 years ago
Closed 15 years ago
#9904 closed enhancement (duplicate)
Serving static files from a different domain.
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | static http |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The base URL of static content should be configurable so that static files can potentially be served from a different (cookie-less) domain. Specifically you should be able to configure the base URL for chrome/* and raw-attachment/* files.
Attachments (0)
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
I also don't think it's a good idea for attachments, so "wontfix" for that. For chrome/*, duplicate of #9683, as Simon said.
Note:
See TracTickets
for help on using tickets.
Attachments are handled under Trac security model, and we should not make provisions for circumventing that by alternative non-Trac configurable access.
That leaves making
htdocs_locationbetter & more useful, which is the topic of #9683.