does Abyss support .htaccess ?

jans · 2004-06-04T13:24:57+00:00

I ned to know if abyss webserver supports the .htaccess and how I can configure abyss to use the .htaccess files. Some kinda short tutorial is prefered because I am totally new to this matter. If someone could help me please ?

Anonymoose

That doesn't actually do the same as the .htaccess directive though unless I'm reading it wrong. The .htaccess directive disallows access to *all files in the directory* and listing the directory. The Abyss version will only block listing the files but allow access if a user knows the exact path - which is where the original question starts...

jans

Anonymoose wrote
That doesn't actually do the same as the .htaccess directive though unless I'm reading it wrong. The .htaccess directive disallows access to *all files in the directory* and listing the directory. The Abyss version will only block listing the files but allow access if a user knows the exact path - which is where the original question starts...

Right, thanks for this clear help, and so we are back to the beginning but now I at least have someone who understands the problem ;-)

iNaNimAtE

Anonymoose wrote
That doesn't actually do the same as the .htaccess directive though unless I'm reading it wrong. The .htaccess directive disallows access to *all files in the directory* and listing the directory. The Abyss version will only block listing the files but allow access if a user knows the exact path - which is where the original question starts...

Which is why I suggested IP banning.
First, Foxified, I wasn't planning on banning anyone. That was a solution I had thought of.
If you ban users from a certain directory and change it to only allow from your IP, then all users will be banned from both the directory and and the files. Also, yes, the way you used .htaccess will ban everyone from both. There is the IndexIgnore command which is more what TRUSTpunk was thinking of.
However, as TRUSTpunk said, there is a bug in the current beta, so you'll have to wait for the new one.

aprelium

Making a directory or some files unreachable for all users (or for some users) is possible in the new version.

jans

aprelium wrote
Making a directory or some files unreachable for all users (or for some users) is possible in the new version.

Q;
1. When and where is this version going to be available ?
2. Does it support the function from the little .htacces file ( non listing, non showing of files in certain maps ? to all visitors from anywhere from the web ?

Anonymoose

The beta version is already available. Look at the additional section at the bottom of the forum.
You should be able to implement the htaccess options you required using the options in the new version, although currently the IP banning is not working correctly, so you'd have to wait for a newer version of the beta.

loose traffic

I'm unsure as to how this would be done.. I'd like to allow linking from my website only (beaconschool.org/~mseverin). I understand how it would be done with an .htaccess file using mod_rewrite function ...

RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?yourdomain\.com/.*$ [NC]
RewriteRule \.(gif|jpg)$ - [F]

I'd appreciate any help :/

aprelium-beta

loose traffic,
This feature is called antileeching and will be available in version 2. Meanwhile, You can download the Beta release of version 2 (see the 2.0 Beta section in this forum) and test it immediatly.

loose traffic

I put this at the very top of my INDEX.PHP

<?php 
$from = getenv("HTTP_REFERER"); 
print("$from"); 
?>

It works in Opera but in IE abyss gives an "Error 200"
I'm working with iframes.. what might error 200 mean
I'll check 2.0 out immediatly

loose traffic

it seems as though there's no exception list to the antileech feature :(

aprelium-beta

loose traffic wrote
I put this at the very top of my INDEX.PHP
<?php 
$from = getenv("HTTP_REFERER"); 
print("$from"); 
?>
It works in Opera but in IE abyss gives an "Error 200"
I'm working with iframes.. what might error 200 mean
I'll check 2.0 out immediatly

Error 200 means that the script was exeuted fine but that it sent no ouput was sent to the server from the script. This happens when $from is empty, i.e., when HTTP_REFERER is empty, i.e., when the browser doesn't send the referrer information.
To solve error 200 problem, change:

print("$from")

print("$from ")

So now, even if $from is empty, the little space will be output.[/code]

aprelium-beta

loose traffic wrote
it seems as though there's no exception list to the antileech feature :(

There is no documentation yet for 2.0 Beta, but to do set antileeching for *.jpg files for example, add /*.jpg to the Antileech scope. That's it.

loose traffic

thanks about the error messages and as for the antileeching.. i meant an exception list to allow certain sites to "leech" ... i'm using abyss to host certain folders on my computer and a members section on a seperate server links to it.. i was hoping to allow access only when members follow that specific link. it seems as though abyss restricts access from ALL outside websites

aprelium

loose traffic wrote
thanks about the error messages and as for the antileeching.. i meant an exception list to allow certain sites to "leech" ... i'm using abyss to host certain folders on my computer and a members section on a seperate server links to it.. i was hoping to allow access only when members follow that specific link. it seems as though abyss restricts access from ALL outside websites

OK, we understand now what you mean. A better antileeching configuration will be available soon. The version you tested is a "test" version, so not everything is perfect :-)

neamtzu

I have the following .htaccess file content:
Options -Indexes
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?mywebsite.com/.*$ [NC]
RewriteRule \.(rar|zip|mp3|ace|avi)$ - [F]
This allows only reffers from mywebsite.com to acces my files in that folder. But i read that htaccess isnt supported by abyss, so can you please tell me how to use this anti-leeching feature with abyss ?

TRUSTAbyss

Download the beta in the beta 2 forum and follow the documentation or look
at my simple example tutorial at http://abyssws.cjb.net , I hope this helps.

admin

neamtzu wrote
I have the following .htaccess file content:
Options -Indexes
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?mywebsite.com/.*$ [NC]
RewriteRule \.(rar|zip|mp3|ace|avi)$ - [F]
This allows only reffers from mywebsite.com to acces my files in that folder. But i read that htaccess isnt supported by abyss, so can you please tell me how to use this anti-leeching feature with abyss ?

Version 2 (that is currently under tests, see the 2.0 Beta section in this forum) has the same feature. It is called antileeching and it doesn't require all these cryptic lines to be configured.

Arctic

A message

Anonymoose

It won't help at all, the question was about anti-leeching, ie blocking hotlinking of files from other sites, not password protecting their own site.

« Previous Page