| Summary: | tracecompass.org doesn't resolve to https://www.eclipse.org/tracecompass/ anymore | ||
|---|---|---|---|
| Product: | Community | Reporter: | Bernd Hufmann <bernd.hufmann> |
| Component: | Website | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bernd.hufmann, eric.poirier, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Bernd Hufmann
Well based on the IP associated with tracecompass.org this looks like it may have been handled by a vserver which is now shutdown(perhaps related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=551276 ?). What I've done is update the DNS record to point tracecompass.org to one of our inbound gateway IPs and submitted a patch to handle the http://tracecompas.org->https://www.eclipse.org/tracecompass redirection. Do we need to do an https://tracecompass.org->https://www.eclipse.org/tracecompass redirection? -M. This should now be fixed. -M. |