Sponsored Content
Full Discussion: HTTP Protocol Version
Operating Systems Solaris HTTP Protocol Version Post 302260267 by cbkihong on Thursday 20th of November 2008 03:48:38 AM
Old 11-20-2008
Your question looks weird. A "normal" HTTP/1.1 server like Apache will serve both HTTP/1.0 and HTTP/1.1 requests. So what exactly do you want to achieve?
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

What is "incompatible protocol version"

have installed a Network Management System at HP and when I tried to connect to Sun for Extractor function, it shows" incompatible protocol version:3". What does it mean? How to slove the problem? Thanks a lot, Emily (1 Reply)
Discussion started by: yaoww
1 Replies

2. UNIX for Advanced & Expert Users

http protocol from UNIX

Is there any way to access http page from UNIX command line.... eg: http://www.abc.xyz (5 Replies)
Discussion started by: bishweshwar
5 Replies

3. AIX

SSH Protocol Version 1

SSH Protocol Version 1 Session Key Retrieval Disable compatibility with version 1 of the protocol can any one advice in this regard and how can I Disable compatibility with version 1 of the protocol Pls advice .. (2 Replies)
Discussion started by: Mr.AIX
2 Replies

4. Web Development

HTTP Headers Reference: HTTP Status-Codes

Hypertext Transfer Protocol -- HTTP/1.1 for Reference - HTTP Headers 10 Status Code Definitions Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. (1 Reply)
Discussion started by: Neo
1 Replies

5. Shell Programming and Scripting

awk script to find time difference between HTTP PUT and HTTP DELETE requests in access.log

Hi, I'm trying to write a script to determine the time gap between HTTP PUT and HTTP DELETE requests in the HTTP Servers access log. Normally client will do HTTP PUT to push content e.g. file_1.txt and 21 seconds later it will do HTTP DELETE, but sometimes the time varies causing some issues... (3 Replies)
Discussion started by: Juha
3 Replies
HTTP::Server::Simple::Authen(3pm)			User Contributed Perl Documentation			 HTTP::Server::Simple::Authen(3pm)

NAME
HTTP::Server::Simple::Authen - Authentication plugin for HTTP::Server::Simple SYNOPSIS
package MyServer; use base qw( HTTP::Server::Simple::Authen HTTP::Server::Simple::CGI); use Authen::Simple::Passwd; sub authen_handler { Authen::Simple::Passwd->new(passwd => '/etc/passwd'); } sub handle_request { my($self, $cgi) = @_; my $user = $self->authenticate or return; ... } MyServer->new->run(); DESCRIPTION
HTTP::Server::Simple::Authen is an HTTP::Server::Simple plugin to allow HTTP authentication. Authentication scheme is pluggable and you can use whatever Authentication protocol that Authen::Simple supports. You can use "authenticate" method whatever you want to authenticate the request. The method returns $username taken from the request if the authentication is successful, and "undef" otherwise. The code in "SYNOPSIS" requires authentication for all the requests and behaves just the same as Apache's "Require valid-user". The following code will explain more about conditioning. sub handle_request { my($self, $cgi) = @_; if ($cgi->path_info =~ m!/foo/!) { my $user = $self->authenticate; return unless defined($user) && length($user) == 8; } ... } This means all the requests to URL "/foo/" require to be authenticated, and usernames with 8 chars long are authorized. METHODS
Your subclass has to override following methods to implement HTTP authentication. authen_handler Should return a valid Authen::Simple instance to authenticate HTTP request (Required). authen_realm Returns a string for Authentication realm to be shown in the browser's dialog box. Defaults to 'Authorized area'. AUTHOR
Tatsuhiko Miyagawa <miyagawa@bulknews.net> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
HTTP::Server::Simple, Authen::Simple perl v5.12.3 2006-01-15 HTTP::Server::Simple::Authen(3pm)
All times are GMT -4. The time now is 02:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy