Serious Thread (ST) - SSI or equivalent to include a page across several domains?
 

All domains are on same box..... will SSI work across server for a few domains?

I need to include links on each page and dont want to update evry page rather one main page the the SSi or whatever will call.


????:helpme

I think it will. Just give it a try!

better include a (pic) in your title next time instead of a (ST) :winkwink: if you know what I mean...

:Graucho :Graucho

:helpme :helpme :helpme

If i dont get help

I wont post funny pics anymore

funny how a serious thread doesnt get any answers

yes, will work with files OR directories, have a few clients that use shared content for members areas, and asl long as everything sits on the same machine, will work fine.

You can do it on the same server easily. if you want to do it across servers you're gonna want to use something like php which if setup properly can do it very easily. (easiest in fact) if you need help hit
36670850

D

Someone help juicy:mad: :mad: :mad:

This is why god gave hosting companies tech support.

this is also helpfull and might help with what you need doing:
http://linux.about.com/library/cmd/blcmdl1_ln.htm

I do that with galleries. Like my gallery list is on one domain and I do a php include of ../www.picshow.net/galdump/teens7.txt or whatever.

SSI won't be able to help as it has no access to any sort of URL wrapper, PHP is something that would work. When compiled with the proper configuration options, you're able to include other files via HTTP.

Keep in mind, though, you will _not_ be able to include PHP code and have it be run on the local server it's being included on.

General syntax would be:

<?php
include("http://www.yoursite.com/includes/include.htm");
?>

Any questions feel free to ICQ me.

Andy

I dont use tech support for educational purposes. I try to figure and learn it myself. :Graucho


I am just teaching myself juicy stuff

In that case you should use PHP includes, you can include basically anything anywhere. If have .php files gives you heartburn there are tricks to avoid that. :Graucho

Yeah, the most effective of which being to either edit the httpd.conf file or use an .htaccess file with the line:


AddType application/x-httpd-php .php .php3 .htm .html

To make .htm and .html files work with the PHP parser.


Edit: Assuming it's an apache webserver.

why not use symbolic links to the file... and then ssi to include.

then update your primary file.

hehe now lets be precise so long as we're teaching juicy the ropes on php. you CAN include remote php code, but you have to treat it well :) you can pop the code as plaintext (non parsed) on one machine (SO insecure it hurts) and include it on another box and EVAL it which works fine... base64encoding and gzipping then removing the code bits helps to secure it a bit if you dont mind a 12 year old figuring it out. :)

but fair's fair, mod is right (and I'm sure he knew all this) you cant just include php code from remote servers as it will be parsed by apache (or whatever) before it gets to you.

dont even get me started on SOAP ;)

D

You can access via SSI files and directories across domains on a single machine. But first you need to set up an alias for each directory (tree) that you want to be able to address in this way.

You do this in httpd.conf and an example would be:
Alias /common /full_server_path_to_one_of_your_domains/common

Using that example, you would then be able to address files and subdirectories in the directory "common" using the same SSI commands as if that directory existed on each domain. BTW this works not only for SSI includes, etc., but also for normal href= calls, img src= etc.

Since it's all on the same server use the absolute path to the file with php include instead, much faster then a http reference.

terry goodkind? milamber?

Yeah. Although, technically, it'd be parsed by PHP before it gets to you. Apache passes it to the PHP parser, which returns the modified code back to Apache to server. ;)

And yes, you _could_ include remote PHP code, using the methods you mentioned. Another would be to use PHP's sockets support to open an https connection to the server with the code, and send a password via POST to retrieve the content. The server could keep an active list of allowed domains/scripts that it will serve, and if you're not on the list, OR you're on it and supply an invalid pass, just spit out an error instead.

Yeah, I didn't pay enough attention to the original post, I thought he wanted to include across separate servers. I agree with the above post (namely because it's right;), including via absolute path will save you some overhead and make for faster response times in general.

Raymond E. Feist , I misspelled it the first time i used it and it stuck after that.