provavelente você nao configurou o htaccess corretamente....

dependendo do ambiente deve usar caminho virtual absoluto

ErrorDocument 404 http://foo.bar/404.htmlconsulte: http://httpd.apache.org/docs/2.0/mod/core.html#errordocument

quanto chmod estude sobre conceitos básicos do Linux

http://en.wikipedia.org/wiki/CHMOD

obs: para simplificar, clientes FTP possui recurso para atribuir chmod a pastas e arquivos

sabe o que é "cliente FTP" ?

vlw mas nao resolvi o problema

estou usando o xammp, e nas configuracoes do apache no ficheiro httpd

habilitei

LoadModule rewrite_module modules/mod_rewrite.so
e tb

<Directory />
 Options FollowSymLinks
 AllowOverride All
 Order deny,allow
 Deny from all
 Satisfy all
</Directory>

mas de qualquer forma não funcionou, estou tentando isso localmente, isso não funciona localmente?

mostra como esta seu htaccess

mostra como esta seu htaccess

htaccess

ErrorDocument 404 /error/404.html

so isso?

experimenta coloca no inicio

RewriteEngine On

igor vlw mas mesmo assim não funcionou

dá o seguinte erro

Not Found

The requested URL /captcha/xdxd was not found on this server.

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

ae eu pensei pode ser que tenha a barra a mais, mas se eu retirar a barra aparece isso

404.html

já não entendo nada, rsrsrsr

nunca trabalhei com htaccess mas somente queria customizar a pagina de erro mas teima em nao funcionar

rapaz, acabei de testar aki, e esta perfeito

meu htaccess esta assim:

RewriteEngine On
RewriteBase /
ErrorDocument 404 http://localhost/testes/404.html

nao sei então pode ser má configuração do apache, mas fiz tudo de acordo com um tutorial para habilitar o htacccess e mesmo assim nao está funcionando

vlw de qualquer maneira

estou tentando testar em localhost se alguem souber vlw

aki foi localhost, e com xampp....cara, na boa, se a sua instalacao do windows for limpa, faça uma instalacao manual do conjunto apache...

vlw igor pelo seu tempo em tentar ajudar, eu instalei o wammp, fui no arquivo httpd na pasta apache e configurei, vou aqui postar o conteudo desse ficheiro para você ver se esta mal configurado

#

This is the main Apache HTTP server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.

In particular, see

<URL:http://httpd.apache.org/docs/2.2/mod/directives.html>

for a discussion of each configuration directive.

Do NOT simply read the instructions in here without understanding

what they do. They're here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.

Configuration and logfile names: If the filenames you specify for many

of the server's control files begin with "/" (or "drive:/" for Win32), the

server will use that explicit path. If the filenames do not begin

with "/", the value of ServerRoot is prepended -- so "logs/foo.log"

with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the

server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., "c:/apache" instead of "c:\apache").

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default. It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

ThreadsPerChild: constant number of worker threads in the server process

MaxRequestsPerChild: maximum number of requests a server process serves

#

ServerRoot: The top of the directory tree under which the server's

configuration, error, and log files are kept.

Do not add a slash at the end of the directory path. If you point

ServerRoot at a non-local disk, be sure to point the LockFile directive

at a local disk. If you wish to share the same ServerRoot for multiple

httpd daemons, you will need to change at least LockFile and PidFile.

#

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, instead of the default. See also the <VirtualHost>

directive.

Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

#

Dynamic Shared Object (DSO) Support

To be able to use the functionality of a module which was built as a DSO you

have to place corresponding `LoadModule' lines at this location so the

directives contained in it are actually available _before_ they are used.

Statically compiled modules (those listed by `httpd -l') do not need

to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so

'Main' server configuration

The directives in this section set up the values used by the 'main'

server, which responds to any requests that aren't handled by a

# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.

All of these directives may appear inside <VirtualHost> containers,

in which case these default settings will be overridden for the

virtual host being defined.

#

ServerAdmin: Your address, where problems with the server should be

e-mailed. This address appears on some server-generated pages, such

as error documents. e.g. admin@your-domain.com

#

ServerName gives the name and port that the server uses to identify itself.

This can often be determined automatically, but we recommend you specify

it explicitly to prevent problems during startup.

If your host doesn't have a registered DNS name, enter its IP address here.

#

DocumentRoot: The directory out of which you will serve your

documents. By default, all requests are taken from this directory, but

symbolic links and aliases may be used to point to other locations.

#

Each directory to which Apache has access can be configured with respect

to which services and features are allowed and/or disabled in that

directory (and its subdirectories).

First, we configure the "default" to be a very restrictive set of

features.

<Directory />
 Options FollowSymLinks
 AllowOverride All
 Order deny,allow
 Deny from all
 Satisfy all
</Directory>

#

Note that from this point forward you must specifically allow

particular features to be enabled - so if something's not working as

you might expect, make sure that you have specifically enabled it

below.

#

This should be changed to whatever you set DocumentRoot to.

<Directory "c:/wamp/www/">

 #
 # Possible values for the Options directive are "None", "All",
 # or any combination of:
 # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
 #
 # Note that "MultiViews" must be named *explicitly* --- "Options All"
 # doesn't give it to you.
 #
 # The Options directive is both complicated and important. Please see
 # [http://httpd.apache.org/docs/2.2/mod/core.html#options](http://httpd.apache.org/docs/2.2/mod/core.html#options)
 # for more information.
 #
 Options Indexes FollowSymLinks

 #
 # AllowOverride controls what directives may be placed in .htaccess files.
 # It can be "All", "None", or any combination of the keywords:
 # Options FileInfo AuthConfig Limit
 #
 AllowOverride all

 #
 # Controls who can get stuff from this server.
 #

onlineoffline tag - don't remove

</Directory>

#

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

<IfModule dir_module>
 DirectoryIndex index.php index.php3 index.html index.htm
</IfModule>

#

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

<FilesMatch "^\.ht">
 Order allow,deny
 Deny from all
</FilesMatch>

#

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a <VirtualHost>

container, error messages relating to that virtual host will be

logged here. If you do define an error logfile for a <VirtualHost>

container, that host's errors will be logged there and not here.

#

LogLevel: Control the number of messages logged to the error_log.

Possible values include: debug, info, notice, warn, error, crit,

alert, emerg.

<IfModule log_config_module>
 #
 # The following directives define some format nicknames for use with
 # a CustomLog directive (see below).
 #
 LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
 LogFormat "%h %l %u %t \"%r\" %>s %b" common

 <IfModule logio_module>
 # You need to enable mod_logio.c to use %I and %O
 LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
 </IfModule>

 #
 # The location and format of the access logfile (Common Logfile Format).
 # If you do not define any access logfiles within a <VirtualHost>
 # container, they will be logged here. Contrariwise, if you *do*
 # define per-<VirtualHost> access logfiles, transactions will be
 # logged therein and *not* in this file.
 #
 CustomLog "c:/wamp/logs/access.log" common

 #
 # If you prefer a logfile with access, agent, and referer information
 # (Combined Logfile Format) you can use the following directive.
 #
 #CustomLog logs/access.log combined
</IfModule>

<IfModule alias_module>
 #
 # Redirect: Allows you to tell clients about documents that used to
 # exist in your server's namespace, but do not anymore. The client
 # will make a new request for the document at its new location.
 # Example:
 # Redirect permanent /foo [http://localhost/bar](http://localhost/bar)

 #
 # Alias: Maps web paths into filesystem paths and is used to
 # access content that does not live under the DocumentRoot.
 # Example:
 # Alias /webpath /full/filesystem/path
 #
 # If you include a trailing / on /webpath then the server will
 # require it to be present in the URL. You will also likely
 # need to provide a <Directory> section to allow access to
 # the filesystem path.

 #
 # ScriptAlias: This controls which directories contain server scripts.
 # ScriptAliases are essentially the same as Aliases, except that
 # documents in the target directory are treated as applications and
 # run by the server when requested rather than as documents sent to the
 # client. The same rules about trailing "/" apply to ScriptAlias
 # directives as to Alias.
 #
 ScriptAlias /cgi-bin/ "cgi-bin/"

</IfModule>

#

"C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased

CGI directory exists, if you have that configured.

<Directory "cgi-bin">
 AllowOverride None
 Options None
 Order allow,deny
 Allow from all
</Directory>

#

Apache parses all CGI scripts for the shebang line by default.

This comment line, the first line of the script, consists of the symbols

pound (#) and exclamation (!) followed by the path of the program that

can execute this specific script. For a perl script, with perl.exe in

the C:\Program Files\Perl directory, the shebang line should be:

#!c:/program files/perl/perl

Note you _must_not_ indent the actual shebang line, and it must be the

first line of the file. Of course, CGI processing must be enabled by

the appropriate ScriptAlias or Options ExecCGI directives for the files

or directory in question.

However, Apache on Windows allows either the Unix behavior above, or can

use the Registry to match files by extention. The command to execute

a file of this type is retrieved from the registry by the same method as

the Windows Explorer would use to handle double-clicking on a file.

These script actions can be configured from the Windows Explorer View menu,

'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit

button allows you to modify the Actions, of which Apache 1.3 attempts to

perform the 'Open' Action, and failing that it will try the shebang line.

This behavior is subject to change in Apache release 2.0.

Each mechanism has it's own specific security weaknesses, from the means

to run a program you didn't intend the website owner to invoke, and the

best method is a matter of great debate.

To enable the this Windows specific behavior (and therefore -disable- the

equivilant Unix behavior), uncomment the following directive:

The directive above can be placed in individual <Directory> blocks or the

.htaccess file, with either the 'registry' (Windows behavior) or 'script'

(Unix behavior) option, and will override this server default option.

#

DefaultType: the default MIME type the server will use for a document

if it cannot otherwise determine one, such as from filename extensions.

If your server contains mostly text or HTML documents, "text/plain" is

a good value. If most of your content is binary, such as applications

or images, you may want to use "application/octet-stream" instead to

keep browsers from trying to display binary files as though they are

text.

<IfModule mime_module>
 #
 # TypesConfig points to the file containing the list of mappings from
 # filename extension to MIME-type.
 #
 TypesConfig conf/mime.types

 #
 # AddType allows you to add to or override the MIME configuration
 # file specified in TypesConfig for specific file types.
 #
 #AddType application/x-gzip .tgz
 #
 # AddEncoding allows you to have certain browsers uncompress
 # information on the fly. Note: Not all browsers support this.
 #
 #AddEncoding x-compress .Z
 #AddEncoding x-gzip .gz .tgz
 #
 # If the AddEncoding directives above are commented-out, then you
 # probably should define those extensions to indicate media types:
 #
 AddType application/x-compress .Z
 AddType application/x-gzip .gz .tgz
 AddType application/x-httpd-php .php
 AddType application/x-httpd-php .php3

 #
 # AddHandler allows you to map certain file extensions to "handlers":
 # actions unrelated to filetype. These can be either built into the server
 # or added with the Action directive (see below)
 #
 # To use CGI scripts outside of ScriptAliased directories:
 # (You will also need to add "ExecCGI" to the "Options" directive.)
 #
 #AddHandler cgi-script .cgi

 # For type maps (negotiated resources):
 #AddHandler type-map var

 #
 # Filters allow you to process content before it is sent to the client.
 #
 # To parse .shtml files for server-side includes (SSI):
 # (You will also need to add "Includes" to the "Options" directive.)
 #
 #AddType text/html .shtml
 #AddOutputFilter INCLUDES .shtml
</IfModule>

#

The mod_mime_magic module allows the server to use various hints from the

contents of the file itself to determine its type. The MIMEMagicFile

directive tells the module where the hint definitions are located.

#

Customizable error responses come in three flavors:

1) plain text 2) local redirects 3) external redirects

Some examples:

#

EnableMMAP and EnableSendfile: On systems that support it,

memory-mapping or the sendfile syscall is used to deliver

files. This usually improves server performance, but must

be turned off when serving from networked-mounted

filesystems or if support for these functions is otherwise

broken on your system.

Supplemental configuration

The configuration files in the conf/extra/ directory can be

included to add extra features or to modify the default configuration of

the server, or you may simply copy their contents here and change as

necessary.

Server-pool management (MPM specific)

Multi-language error messages

Fancy directory listings

Language settings

User home directories

Real-time info on requests and configuration

Virtual hosts

Local access to the Apache HTTP Server Manual

Distributed authoring and versioning (WebDAV)

Various default settings

Secure (SSL/TLS) connections

Note: The following must must be present to support

starting without SSL on platforms with no /dev/random equivalent

but a statically compiled-in mod_ssl.

Include "c:/wamp/alias/*"

bom, o mod_rewrie ae esta ativado, o erro continua?

ErrorDocument 404 http://localhost/pasta1/pasta2/pasta3/arquivo.html

se nao tiver dentro de pasta eh so por http://localhost/arquivo.html

nao funciona na mesma não sei o que pode ser, vlw

resolvido, tinha colocado o htaccess dentro da pasta do sistema que eu estava testando mudei o htaccess para a pasta www e funfou. Acho que é pk no apache ta mesmo essa pasta na configuracao, :)

agora entendi isso

DocumentRoot "c:/wamp/www"

auhasuahsuah

desculpem lá ter-vos feito perder tempo, mas eu nunca tinha configurado nada no apache nem trabalhado com htaccess

vlw por toda a vossa ajuda