Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Document footers 1
- Thread starter rewebb
- Start date
-
1
- #2
Hi rewebb
You are right global footers don't work in .asp files. This is from the microsoft site ( and includes a workaround:
[bold]SYMPTOMS[/bold]
Document footers do not work with ASP files.
[bold]CAUSE[/bold]
This occurs because ASP files (and other ISAPI applications) feed their responses to the client directly and have control of keeping the connection open or closing it.
Because IIS cannot determine when ASP (or ISAPI applications for that matter) has completed its request, it cannot determine when to send the footer, or even if it has a connection to send it on.
[bold]RESOLUTION[/bold]
To resolve this problem, use .htm or .html files instead of ASP files, or add server-side include (SSI) directives to the ASP files to specify the footer file.
[end]
I don't know asp very well, but I work with ColdFusion and the Fusebox methodology ( and what we do is create a file for each site (at the site root) which contains global variables (like datasource name, etc). You could create something similar, specify the name of the document footer and then include that page in every other page on the site. Then at the bottom of each file include the value of the footer variable. That way if you change your footer's name you only have to change it in one page on each site.
Hope that helps! The New Zealand Site
You are right global footers don't work in .asp files. This is from the microsoft site ( and includes a workaround:
[bold]SYMPTOMS[/bold]
Document footers do not work with ASP files.
[bold]CAUSE[/bold]
This occurs because ASP files (and other ISAPI applications) feed their responses to the client directly and have control of keeping the connection open or closing it.
Because IIS cannot determine when ASP (or ISAPI applications for that matter) has completed its request, it cannot determine when to send the footer, or even if it has a connection to send it on.
[bold]RESOLUTION[/bold]
To resolve this problem, use .htm or .html files instead of ASP files, or add server-side include (SSI) directives to the ASP files to specify the footer file.
[end]
I don't know asp very well, but I work with ColdFusion and the Fusebox methodology ( and what we do is create a file for each site (at the site root) which contains global variables (like datasource name, etc). You could create something similar, specify the name of the document footer and then include that page in every other page on the site. Then at the bottom of each file include the value of the footer variable. That way if you change your footer's name you only have to change it in one page on each site.
Hope that helps! The New Zealand Site
- Thread starter
- #3
Thanks for that xor - I knew that we had the option of SSI's or Include files, but that completely defeats the purpose of the IIS Document Footer feature :-(
But there is no alternative because, in this case, IIS is rubbish.
The M$ article made me laugh when it said "To resolve this problem, use .htm or .html files instead of ASP files"...
Rob W
But there is no alternative because, in this case, IIS is rubbish.
The M$ article made me laugh when it said "To resolve this problem, use .htm or .html files instead of ASP files"...
Rob W
Yes I reckon! In other words...
To resolve this problem, use use something other than our technology
Good you're able to laugh about it anyway
Donna The New Zealand Site
To resolve this problem, use use something other than our technology
Good you're able to laugh about it anyway
Donna The New Zealand Site
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question