View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 385 | WADF | Core | public | 18 Aug 2011 09:14 | 20 Feb 2012 21:08 |
| Reporter | mrosenquist | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Product Version | 0.13.5 | ||||
| Summary | 385: Wadf to warn when a vhostX_name contains an underscore | ||||
| Description | Wadf to warn when a vhostX_name contains an underscore - This is not allow in a DNS level. Valid characters for a subdomain are [A-Z], [0-9] and - - Cookies on internet explorer only work with URLs whichs follows the RCF 2396 (Uniform Resource Identifiers) | ||||
| Steps To Reproduce | 1. Deploy a site with an underscore in the domain. 2. Go to a part of the site which sets cookies using IE6 or greater 3. Check if the cookie is set | ||||
| Tags | No tags attached. | ||||
|
|
It's 100% true that underscores in hostnames are completely invalid and should definitely not be used. That's basic DNS. In general I think delving too much into the content of macros to validate the content is beyond the scope of WADF as a templating tool as it crosses the boundary where WADF treats the content of macros as opaque (except for replacing ** and %%). |
|
|
Closing on the basis that this should be done in a different layer, e.g. Apache HTTPD |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 18 Aug 2011 09:14 | mrosenquist | New Issue | |
| 18 Aug 2011 10:06 | timj | Note Added: 388 | |
| 18 Aug 2011 10:06 | timj | Severity | major => feature |
| 18 Aug 2011 10:06 | timj | Reproducibility | have not tried => N/A |
| 20 Feb 2012 21:08 | timj | Note Added: 445 | |
| 20 Feb 2012 21:08 | timj | Status | new => closed |
| 20 Feb 2012 21:08 | timj | Resolution | open => won't fix |
