Co/sub-domains without rewritten URLs

[andrusha]

can someone help which line to comment out????

[falko]

Ehm, what exactly is your problem?

[andrusha]

i figured out thank you .....

[schmidtedv]

I did this by patching line 1410 in ISPConfig 2.2.24...works nicely.

However, there seems to be a little sideeffect:

Error-Pages are not shown anymore for these subdomains. If I just try to get a non-existant-link, I only get the standard error-page from IE. It doesn't matter to take my own error-pages or the once that come with ISPConfig. So this seems to be a little disadvantage with this patch...

[DUCKFACE]

okey ... i made the changes ..
the index.php is visible and url is a.sometnin.com

but .. when i watn to procede with anotehr page .. i got this ..

Not Found

The requested URL /page.php was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

what gets wrong ..

isp is 2.2.32
________
VIDEOS PORNOS
________
LIST OF MAZDA FACILITIES PICTURE

[falko]

What exactly do you want to achieve, and what have you done so far?

[DUCKFACE]

http://a.sometni.com to looks like a.sopmetni.com not like sometnin.com/a/

when i
"\nRewriteRule ^/(.*)$ http://".$servername.$domain["domain_weiterleitung"]."$1 [R]";
remove the - [R] in the address bar address is visible like i want - s.sometin.com
but ... the links between files r missing
for example when i browsing the pages when [R] is there .. i can open page1.php from page.php .
but when [R] is removed -> page1.php gets 404 page not found
________
Buy no2 vaporizer

[DUCKFACE]

any idea whats wrong ?
________
Subaru Srd-1 History
________
Ford Vx54 Platform Picture
________
Ordinary Life Insurance Advice

[t-mug]

1.) First thing is: I have had run webs in such pseudo subdomains (by [R]-deletion-hack) without errors. But I had always to inject an apache directive into this kind of co-subby-domain-thingy like "RewriteBase /" (written into .htaccess). A CMS like e. g. Drupal runs this way without problems.

2.) The summary for me is that this is a bad replacement for real Apache subdomains, which can have always an own DOCUMENT_ROOT, own statistics etc. - However, good news: there is a way to hand real Apache subdomains to customers! How? Let them be resellers!. You can this way control:

1. how many "webs" (= subdomains) customers may have, e. g. "3"
2. how many domains customers may have, e. g. "1"
3. how many diskspace of the "reseller" space a web/subdomain may have, e. g. 500MB of "resellers" 2GB total;
4. if or if not an customer is allowed to inject own apache directives (surely not recommended)
5. that the customer may not edit DNS resords.

Thats a lot! An almost perfect solution. Except maybe: some irritations based on hardcoded naming conventions, like the term "Reseller" or "Customers" inside the navigation.

Anyway, whatever works ...