Sponsored Content
Top Forums UNIX for Advanced & Expert Users mod_ssl redirect to site if client does not have valid certificate Post 302217133 by Esaia on Tuesday 22nd of July 2008 03:08:24 AM
Old 07-22-2008
Hello!

Ah now I get what you mean!

xx.xx.xx.xx - - [22/Jul/2008:09:04:07 +0200] "GET /wiki/index.php/Main_Page HTTP/1.1" 403 -

This is what I get, I've added the following line in my vhost entry:
ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var

But no success yet.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Mod_ssl patch for Apache server v2.0.49

Hi there, Please help, anyone know where to download latest Mod_SSL patch for Apache server v2.0.49 . Have tried www.apache.org but there is not latest patch available. (8 Replies)
Discussion started by: e_jeffhang
8 Replies

2. Web Development

Apache:mod_ssl:Error: Private key not found

hi folks, I have Apache 2.2.8 running on Red Hat Enterprise Linux Server release 5 (Tikanga). I have installed a purchased certificate on my server. Upon restarting httpd, I get the following error: # /etc/init.d/httpd start Apache/2.2.8 mod_ssl/2.2.8 (Pass Phrase Dialog) Some of your... (0 Replies)
Discussion started by: nemotech
0 Replies

3. Programming

Unable to use libcurl to access a site requiring client authentication

I’m using the below snipped for setting the certificate and key for client authentication. curl_easy_setopt(curl,CURLOPT_SSLCERT,"clientCert.pem"); curl_easy_setopt(curl,CURLOPT_SSLCERTPASSWD,"changeit"); curl_easy_setopt(curl,CURLOPT_SSLCERTTYPE,"PEM"); ... (2 Replies)
Discussion started by: old_as_a_fossil
2 Replies

4. UNIX for Dummies Questions & Answers

Calling a webservice and pass a client certificate

Hi, I am trying to call a http soap webservice using curl command , I have tried the below option but I am getting a failure . curl -H "Content-Type: text/xml; charset=utf-8" -H SOAPAction:" -d @Request.xml -X POST... (1 Reply)
Discussion started by: IshuGupta
1 Replies

5. UNIX for Dummies Questions & Answers

Sign Soap Message from client certificate from UNIX

I have to call a webservice , I need to pass the static request from Unix which should have message signing details in the soap header . I am using cURL command for this. I do not have java , I need to do it through Unix only . Below is the kind of Soap envelop I want to wrap around my request .... (0 Replies)
Discussion started by: IshuGupta
0 Replies

6. IP Networking

Does cisco 1921 router support site to site VPNs using IPSec?

Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? " A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies

7. Red Hat

To download mod_ssl for Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga)

Hi, Anyone know how and where to download mod_ssl package into Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga) ? could you also show what's the procedure to apply the mod_ssl into the server and how to apply the digital cert into apache server and so on. Thanks. (1 Reply)
Discussion started by: ckwan
1 Replies

8. UNIX for Advanced & Expert Users

Does vsftpd support user access with client certificate with priv/pub key + vsftpd certificate?

:rolleyes:I am trying to setup all certificate based client-server environment in Linux using vsftpd and curl with openssl. I would like to make a user access with vsftpd certificate and user own client certificate (self-signed) with private/public key. I don't see google posts about the my plan... (4 Replies)
Discussion started by: gogogo
4 Replies

9. UNIX for Beginners Questions & Answers

How to install new certificate in HPUX client store?

We have a HPUX server that talks to a web service. We recently updated the web service certificate to a new SHA256 cert that has an updated intermediate cert. The HPUX server is now unable to connect because it cannot validate the cert chain due to it not having the new intermediate CA cert. I... (0 Replies)
Discussion started by: techmattr
0 Replies

10. Programming

Python- Client and server certificate validation

Hello Team, I have to verify the Client server certificate validation in HTTPS request(SSL hand shake before the actual HTTPS post request), And tried various ways and failed to verify it successfully. here are the trials and errors, resp = requests.post(url, req, verify=True, timeout=5,... (0 Replies)
Discussion started by: chandana.hs
0 Replies
DAV::Response(3)					User Contributed Perl Documentation					  DAV::Response(3)

NAME
HTTP::DAV::Response - represents a WebDAV HTTP Response (ala HTTP::Response) SYNOPSIS
require HTTP::DAV::Response; DESCRIPTION
The HTTP::DAV::Response class encapsulates HTTP style responses. A response consists of a response line, some headers, and (potentially empty) content. HTTP::DAV::Response is a subclass of "HTTP::Response" and therefore inherits its methods. (HTTP::Response in turn inherits it's methods from "HTTP::Message"). Therefore, this class actually inherits a rich library of functions. You are more likely wanting to read the "HTTP::Response" class as opposed to this class. Instances of this class are usually created by a "HTTP::DAV::Resource" object after it has performed some request (such as get, lock, delete, etc). You use the object to analyse the success or otherwise of the request. HTTP::DAV::Response was created to handle two extra functions that normal HTTP Responses don't require: - WebDAV reponses have 6 extra error codes: 102, 207, 422, 423, 424 and 507. Older versions of the LWP's C<HTTP::Status> class did not have these extra codes. These were added. - WebDAV responses can actually contain more than one response (and often DO contain more than one) in the form of a "Multistatus". These multistatus responses come in the form of an XML document. HTTP::DAV::Response can accurately parse these XML responses and emulate the normal of the C<HTTP::Response>. HTTP::DAV::Response transparently implements these extra features without the user having to be aware, so you really should be reading the "HTTP::Response" documentation for most of the things you want to do (have I already said that?). There are only a handful of custom functions that HTTP::DAV::Response returns and those are to handle multistatus requests, "messages()" and "codes()". The six extra status codes that DAV servers can be returned in an HTTP Response are: 102 => "Processing. Server has accepted the request, but has not yet completed it", 207 => "Multistatus", 422 => "Unprocessable Entity. Bad client XML sent?", 423 => "Locked. The source or destination resource is locked", 424 => "Failed Dependency", 507 => "Insufficient Storage. The server is unable to store the request", See "HTTP::Status" for the rest. HANDLING A MULTISTATUS
So, many DAV requests may return a multistatus ("207 multistatus") instead of, say, "200 OK" or "403 Forbidden". The HTTP::DAV::Response object stores each "response" sent back in the multistatus. You access them by array number. The following code snippet shows what you will normally want to do: ... $response = $resource->lock(); if ( $response->is_multistatus() ) { foreach $num ( 0 .. $response->response_count() ) { ($err_code,$mesg,$url,$desc) = $response->response_bynum($num); print "$mesg ($err_code) for $url "; } } Would produce something like this: Failed Dependency (424) for /test/directory Locked (423) for /test/directory/file3 This says that we couldn't lock /test/directory because file3 which exists inside is already locked by somebody else. METHODS
is_multistatus This function takes no arguments and returns a 1 or a 0. For example: if ($response->is_multistatus() ) { } If the HTTP reply had "207 Multistatus" in the header then that indicates that there are multiple status messages in the XML content that was returned. In this event, you may be interested in knowing what the individual messages were. To do this you would then use "messages". response_count Takes no arguments and returns "the number of error responses -1" that we got. Why -1? Because usually you will want to use this like an array operator: foreach $num ( 0 .. $response->response_count() ) { print $response->message_bynum(); } response_bynum Takes one argument, the "response number" that you're interested in. And returns an array of details: ($code,$message,$url,$description) = response_bynum(2); where $code - is the HTTP error code (e.g. 403, 423, etc). $message - is the associated message for that error code. $url - is the url that this error applies to (recall that there can be multiple responses within one response and they all relate to one URL) $description - is server's attempt at an english description of what happened. code_bynum Takes one argument, the "response number" that you're interested in, and returns it's code. E.g: $code = $response->code_bynum(1); See "response_bynum()" message_bynum Takes one argument, the "response number" that you're interested in, and returns it's message. E.g: $code = $response->message_bynum(1); See "response_bynum()" url_bynum Takes one argument, the "response number" that you're interested in, and returns it's url. E.g: $code = $response->message_bynum(1); See "response_bynum()" description_bynum Takes one argument, the "response number" that you're interested in, and returns it's description. E.g: $code = $response->message_description(1); See "response_bynum()" messages Takes no arguments and returns all of the messages returned in a multistatus response. If called in a scalar context then all of the messages will be returned joined together by newlines. If called in an array context the messages will be returned as an array. $messages = $response->messages(); e.g. $messages eq "Forbidden Locked"; @messages = $response->messages(); e.g. @messages eq ["Forbidden", "Locked"]; This routine is a variant on the standard "HTTP::Response" "message()". perl v5.12.1 2010-07-05 DAV::Response(3)
All times are GMT -4. The time now is 10:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy