`
jayjayjays
  • 浏览: 218540 次
  • 性别: Icon_minigender_1
  • 来自: 北京
社区版块
存档分类
最新评论

winXP下Apache1.3+php5.0 配置及应射文件的配置(inber write)

阅读更多

以前我个人用apache是老是懂不懂,装上不会玩儿,呵呵,也许是受学java的影响(配置 tomcat 的xml文件) 摸索着在XP下先装了apache 1.3 因为我的服务器上装有IIS所以我把httpd.conf文件中的port 80 改为83然后又试着根具文档的说明配置让它支持PHP5,呵呵竟然成了;然后又想IIS里有虚拟目录,管理文件方便,apache应该有这方面的服务,于是就看文档,试着配置,竟然弄成了,哈哈,可以把文件放在别的地方执行而不必都放在htdocs目录下了,这是我的一个小乐趣,也希望与大家分享,apache这方面我是个菜鸟,希望在今后的学习中也会更多的深入。于是我又开了这个专题《APACHE》也算是学习笔记吧,费话不多说了,看看我的配置经过吧。

1首先安apache1.3然后配置httpd.conf 文件将端口改为不被占用的端口,启动。

Apache/1.3.31 (Win32) running...

2安装PHP5时选择apache服务器,安完后配置httpd.conf

3应射目录(不太了解别的地方叫什么,我这里就叫它了)

找到以下代码

    Alias /manual/ "D:/Apache/Apache/htdocs/manual/"

    <Directory "D:/Apache/Apache/htdocs/manual">
        Options Indexes FollowSymlinks MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

在其后加入你想要做的应射别名及物理目录例:

    Alias /inber/ "F:/public_php/"

    <Directory "F:/public_php/">
        Options Indexes FollowSymlinks MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

其中 inber为应射名windows中叫虚拟目录然后在<directory 后指定物理目录,这样就可以以http://localhost:83/inber来访问其下的应用文件了

4,让apache支持PHP5

找到 ScriptAlias 文档说明在所有的应用后比如

   ScriptAlias /cgi-bin/ "D:/Apache/Apache/cgi-bin/"

在其后面加入支持PHP的信息描述如:

  ScriptAlias /cgi-bin/ "d:/Apache/Apache/cgi-bin"

  ScriptAlias /php/ "d:/php/"
  AddType application/x-httpd-php .php
  AddType application/x-httpd-php .php3
  AddType application/x-httpd-php .php4
  Action application/x-httpd-php "/php/php-cgi.exe"

放一下测试文件phpinfo.php到F:/public_php 内容为<? phpinfo(); ?>刚才我们已经做了应射目录 inber了

好了我们可以这样访问它了 http://localhost:83/inber/phpinfo.php

 以下为httpd.conf的配置文件:

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/> for detailed information about
# the directives.
#
# 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. 
#
# After this file is processed, the server will look for and process
# D:/Apache/Apache/conf/srm.conf and then D:/Apache/Apache/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# 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 "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/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.
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone.  Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
ServerRoot "D:/Apache/Apache"

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile logs/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this.  But if yours does (you'll know because
# this file will be  created when you run Apache) then you *must* ensure that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile logs/apache_runtime_status

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order.  The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity. 
# The commented-out values below are the built-in defaults.  You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

#
# Apache on Win32 always creates one child process to handle requests.  If it
# dies, another child process is created automatically.  Within the child
# process multiple threads handle incoming requests.  The next two
# directives control the behaviour of the threads and processes.
#

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies.  The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources.  On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries.  For Win32, set this value to zero (unlimited)
# unless advised otherwise.
#
# NOTE: This value does not include keepalive requests after the initial
#       request per connection. For example, if a child process handles
#       an initial request and 10 subsequent "keptalive" requests, it
#       would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0

#
# Number of concurrent threads (i.e., requests) the server will allow.
# Set this value according to the responsiveness of the server (more
# requests active at once means they're all handled more slowly) and
# the amount of system resources you'll allow the server to consume.
#
ThreadsPerChild 50

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80

#
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#
#BindAddress *

#
# 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.
# Please read the file README.DSO in the Apache 1.3 distribution for more
# details about the DSO mechanism and run `apache -l' for the list of already
# built-in (statically linked and thus always available) modules in your Apache
# binary.
#
# Note: The order in which modules are loaded is important.  Don't change
# the order below without expert advice.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule status_module modules/mod_status.so
#LoadModule info_module modules/mod_info.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule rewrite_module modules/mod_rewrite.so
#LoadModule anon_auth_module modules/mod_auth_anon.so
#LoadModule dbm_auth_module modules/mod_auth_dbm.so
#LoadModule digest_auth_module modules/mod_auth_digest.so
#LoadModule digest_module modules/mod_digest.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so

#
#  Reconstruction of the complete module list from all available modules
#  (static and shared ones) to achieve correct module execution order.
#
# The modules listed below, without a corresponding LoadModule directive,
# are static bound into the standard Apache binary distribution for Windows.
#
# Note: The order in which modules are loaded is important.  Don't change
# the order below without expert advice.
#
# [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE, UPDATE THIS TOO!]
ClearModuleList
#AddModule mod_vhost_alias.c
AddModule mod_env.c
AddModule mod_log_config.c
#AddModule mod_mime_magic.c
AddModule mod_mime.c
AddModule mod_negotiation.c
#AddModule mod_status.c
#AddModule mod_info.c
AddModule mod_include.c
AddModule mod_autoindex.c
AddModule mod_dir.c
AddModule mod_isapi.c
AddModule mod_cgi.c
AddModule mod_asis.c
AddModule mod_imap.c
AddModule mod_actions.c
#AddModule mod_speling.c
AddModule mod_userdir.c
AddModule mod_alias.c
#AddModule mod_rewrite.c
AddModule mod_access.c
AddModule mod_auth.c
#AddModule mod_auth_anon.c
#AddModule mod_auth_dbm.c
#AddModule mod_auth_digest.c
#AddModule mod_digest.c
#AddModule mod_proxy.c
#AddModule mod_cern_meta.c
#AddModule mod_expires.c
#AddModule mod_headers.c
#AddModule mod_usertrack.c
#AddModule mod_unique_id.c
AddModule mod_so.c
AddModule mod_setenvif.c


#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On

### Section 2: '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.
#

#
# Port: The port to which the standalone server listens.  Certain firewall
# products must be configured before Apache can listen to a specific port.
# Other running httpd servers will also interfere with this port.  Disable
# all firewall, security, and other services if you encounter problems.
# To help diagnose problems use the Windows NT command NETSTAT -a
#
Port 83

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.
#
ServerAdmin webmaster@inber.51.net

#
# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
#
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
#
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#
ServerName inber


#
# 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.
#
DocumentRoot "D:/Apache/Apache/htdocs"

#
# 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
# permissions. 
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
</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 "D:/Apache/Apache/htdocs">

#
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
    Options Indexes FollowSymLinks MultiViews

#
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
#
    AllowOverride None

#
# Controls who can get stuff from this server.
#
    Order allow,deny
    Allow from all
</Directory>

#
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
#
# Under Win32, we do not currently try to determine the home directory of
# a Windows login, so a format such as that below needs to be used.  See
# the UserDir documentation for details.
#
<IfModule mod_userdir.c>
    UserDir "D:/Apache/Apache/users/"
</IfModule>

#
# Control access to UserDir directories.  The following is an example
# for a site where these directories are restricted to read-only.
#
#<Directory "D:/Apache/Apache/users">
#    AllowOverride FileInfo AuthConfig Limit
#    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#    <Limit GET POST OPTIONS PROPFIND>
#        Order allow,deny
#        Allow from all
#    </Limit>
#    <LimitExcept GET POST OPTIONS PROPFIND>
#        Order deny,allow
#        Deny from all
#    </LimitExcept>
#</Directory>

#
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index.  Separate multiple entries with spaces.
#
<IfModule mod_dir.c>
    DirectoryIndex index.html
</IfModule>

#
# AccessFileName: The name of the file to look for in each directory
# for access control information.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess files from being viewed by
# Web clients.  Since .htaccess files often contain authorization
# information, access is disallowed for security reasons.  Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files.  If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
#
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</Files>

#
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#
#CacheNegotiatedDocs

#
# UseCanonicalName:  (new for 1.3)  With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name.  With this setting off, Apache will
# use the hostname:port that the client supplied, when possible.  This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
#
UseCanonicalName On

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
<IfModule mod_mime.c>
    TypesConfig conf/mime.types
</IfModule>

#
# DefaultType is 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.
#
DefaultType text/plain

#
# 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.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
#
<IfModule mod_mime_magic.c>
    MIMEMagicFile conf/magic
</IfModule>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# 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.
#
ErrorLog logs/error.log

#
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# 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
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# 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 logs/access.log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog logs/referer.log referer
#CustomLog logs/agent.log agent

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

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of:  On | Off | EMail
#
ServerSignature On

#
# 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:
#
#ScriptInterpreterSource registry
#
# 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.
#

#
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
#
<IfModule mod_alias.c>

    #
    # Note that if you include a trailing / on fakename then the server will
    # require it to be present in the URL.  So "/icons" isn't aliased in this
    # example, only "/icons/".  If the fakename is slash-terminated, then the
    # realname must also be slash terminated, and if the fakename omits the
    # trailing slash, the realname must also omit it.
    #
    Alias /icons/ "D:/Apache/Apache/icons/"

    <Directory "D:/Apache/Apache/icons">
        Options Indexes MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

    # This Alias will project the on-line documentation tree under /manual/
    # even if you change the DocumentRoot. Comment it if you don't want to
    # provide access to the on-line documentation.
    #
    Alias /manual/ "D:/Apache/Apache/htdocs/manual/"

    <Directory "D:/Apache/Apache/htdocs/manual">
        Options Indexes FollowSymlinks MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

    Alias /inber/ "F:/public_php/"

    <Directory "F:/public_php/">
        Options Indexes FollowSymlinks MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the realname 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/ "D:/Apache/Apache/cgi-bin/"

  ScriptAlias /cgi-bin/ "d:/Apache/Apache/cgi-bin"

  ScriptAlias /php/ "d:/php/"
  AddType application/x-httpd-php .php
  AddType application/x-httpd-php .php3
  AddType application/x-httpd-php .php4
  Action application/x-httpd-php "/php/php-cgi.exe"

 

    #
    # "D:/Apache/Apache/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    #
    <Directory "D:/Apache/Apache/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>

 


</IfModule>
# End of aliases.

#
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Format: Redirect old-URI new-URL
#

#
# Directives controlling the display of server-generated directory listings.
#
<IfModule mod_autoindex.c>

    #
    # FancyIndexing is whether you want fancy directory indexing or standard
    #
    # Note, add the option TrackModified to the IndexOptions default list only
    # if all indexed directories reside on NTFS volumes.  The TrackModified flag
    # will report the Last-Modified date to assist caches and proxies to properly
    # track directory changes, but it does _not_ work on FAT volumes.
    #
    IndexOptions FancyIndexing

    #
    # AddIcon* directives tell the server which icon to show for different
    # files or filename extensions.  These are only displayed for
    # FancyIndexed directories.
    #
    AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

    AddIconByType (TXT,/icons/text.gif) text/*
    AddIconByType (IMG,/icons/image2.gif) image/*
    AddIconByType (SND,/icons/sound2.gif) audio/*
    AddIconByType (VID,/icons/movie.gif) video/*

    AddIcon /icons/binary.gif .bin .exe
    AddIcon /icons/binhex.gif .hqx
    AddIcon /icons/tar.gif .tar
    AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
    AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
    AddIcon /icons/a.gif .ps .ai .eps
    AddIcon /icons/layout.gif .html .shtml .htm .pdf
    AddIcon /icons/text.gif .txt
    AddIcon /icons/c.gif .c
    AddIcon /icons/p.gif .pl .py
    AddIcon /icons/f.gif .for
    AddIcon /icons/dvi.gif .dvi
    AddIcon /icons/uuencoded.gif .uu
    AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
    AddIcon /icons/tex.gif .tex
    AddIcon /icons/bomb.gif core

    AddIcon /icons/back.gif ..
    AddIcon /icons/hand.right.gif README
    AddIcon /icons/folder.gif ^^DIRECTORY^^
    AddIcon /icons/blank.gif ^^BLANKICON^^

    #
    # DefaultIcon is which icon to show for files which do not have an icon
    # explicitly set.
    #
    DefaultIcon /icons/unknown.gif

    #
    # AddDescription allows you to place a short description after a file in
    # server-generated indexes.  These are only displayed for FancyIndexed
    # directories.
    # Format: AddDescription "description" filename
    #
    #AddDescription "GZIP compressed document" .gz
    #AddDescription "tar archive" .tar
    #AddDescription "GZIP compressed tar archive" .tgz

    #
    # ReadmeName is the name of the README file the server will look for by
    # default, and append to directory listings.
    #
    # HeaderName is the name of a file which should be prepended to
    # directory indexes.
    #
    ReadmeName README
    HeaderName HEADER

    #
    # IndexIgnore is a set of filenames which directory indexing should ignore
    # and not include in the listing.  Shell-style wildcarding is permitted.
    #
    IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

</IfModule>
# End of indexing directives.

#
# Document types.
#
<IfModule mod_mime.c>

    #
    # AddType allows you to tweak mime.types without actually editing it, or to
    # make certain files to be certain types.
    #
    AddType application/x-tar .tgz

    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    # Despite the name similarity, the following Add* directives have nothing
    # to do with the FancyIndexing customization directives above.
    #
    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

    #
    # AddLanguage allows you to specify the language of a document. You can
    # then use content negotiation to give a browser a file in a language
    # it can understand.
    #
    # Note 1: The suffix does not have to be the same as the language
    # keyword --- those with documents in Polish (whose net-standard
    # language code is pl) may wish to use "AddLanguage pl .po" to
    # avoid the ambiguity with the common suffix for perl scripts.
    #
    # Note 2: The example entries below illustrate that in quite
    # some cases the two character 'Language' abbreviation is not
    # identical to the two character 'Country' code for its country,
    # E.g. 'Danmark/dk' versus 'Danish/da'.
    #
    # Note 3: In the case of 'ltz' we violate the RFC by using a three char
    # specifier. But there is 'work in progress' to fix this and get
    # the reference data for rfc1766 cleaned up.
    #
    # Danish (da) - Dutch (nl) - English (en) - Estonian (ee)
    # French (fr) - German (de) - Greek-Modern (el)
    # Italian (it) - Korean (kr) - Norwegian (no) - Norwegian Nynorsk (nn)
    # Portugese (pt) - Luxembourgeois* (ltz)
    # Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cs)
    # Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
    # Russian (ru)
    #
    AddLanguage da .dk
    AddLanguage nl .nl
    AddLanguage en .en
    AddLanguage et .ee
    AddLanguage fr .fr
    AddLanguage de .de
    AddLanguage el .el
    AddLanguage he .he
    AddCharset ISO-8859-8 .iso8859-8
    AddLanguage it .it
    AddLanguage ja .ja
    AddCharset ISO-2022-JP .jis
    AddLanguage kr .kr
    AddCharset ISO-2022-KR .iso-kr
    AddLanguage nn .nn
    AddLanguage no .no
    AddLanguage pl .po
    AddCharset ISO-8859-2 .iso-pl
    AddLanguage pt .pt
    AddLanguage pt-br .pt-br
    AddLanguage ltz .lu
    AddLanguage ca .ca
    AddLanguage es .es
    AddLanguage sv .sv
    AddLanguage cs .cz .cs
    AddLanguage ru .ru
    AddLanguage zh-TW .zh-tw
    AddCharset Big5         .Big5    .big5
    AddCharset WINDOWS-1251 .cp-1251
    AddCharset CP866        .cp866
    AddCharset ISO-8859-5   .iso-ru
    AddCharset KOI8-R       .koi8-r
    AddCharset UCS-2        .ucs2
    AddCharset UCS-4        .ucs4
    AddCharset UTF-8        .utf8

    # LanguagePriority allows you to give precedence to some languages
    # in case of a tie during content negotiation.
    #
    # Just list the languages in decreasing order of preference. We have
    # more or less alphabetized them here. You probably want to change this.
    #
    <IfModule mod_negotiation.c>
        LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv tw
    </IfModule>

    #
    # 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 command (see below)
    #
    # If you want to use server side includes, or CGI outside
    # ScriptAliased directories, uncomment the following lines.
    #
    # To use CGI scripts:
    #
    #AddHandler cgi-script .cgi

    #
    # To use server-parsed HTML files
    #
    #AddType text/html .shtml
    #AddHandler server-parsed .shtml

    #
    # Uncomment the following line to enable Apache's send-asis HTTP file
    # feature
    #
    #AddHandler send-as-is asis

    #
    # If you wish to use server-parsed imagemap files, use
    #
    #AddHandler imap-file map

    #
    # To enable type maps, you might want to use
    #
    #AddHandler type-map var

</IfModule>
# End of document types.

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# MetaDir: specifies the name of the directory in which Apache can find
# meta information files. These files contain additional HTTP headers
# to include when sending the document
#
#MetaDir .web

#
# MetaSuffix: specifies the file name suffix for the file containing the
# meta information.
#
#MetaSuffix .meta

#
# Customizable error response (Apache style)
#  these come in three flavors
#
#    1) plain text
#ErrorDocument 500 "The server made a boo boo.
#  n.b.  the single leading (") marks it as text, it does not get output
#
#    2) local redirects
#ErrorDocument 404 /missing.html
#  to redirect to local URL /missing.html
#ErrorDocument 404 /cgi-bin/missing_handler.pl
#  N.B.: You can redirect to a script or a document using server-side-includes.
#
#    3) external redirects
#ErrorDocument 402 http://www.example.com/subscription_info.html
#  N.B.: Many of the environment variables associated with the original
#  request will *not* be available to such a script.

#
# Customize behaviour based on the browser
#
<IfModule mod_setenvif.c>

    #
    # The following directives modify normal HTTP response behavior.
    # The first directive disables keepalive for Netscape 2.x and browsers that
    # spoof it. There are known problems with these browser implementations.
    # The second directive is for Microsoft Internet Explorer 4.0b2
    # which has a broken HTTP/1.1 implementation and does not properly
    # support keepalive when it is used on 301 or 302 (redirect) responses.
    #
    BrowserMatch "Mozilla/2" nokeepalive
    BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0

    #
    # The following directive disables HTTP/1.1 responses to browsers which
    # are in violation of the HTTP/1.0 spec by not being able to grok a
    # basic 1.1 response.
    #
    BrowserMatch "RealPlayer 4\.0" force-response-1.0
    BrowserMatch "Java/1\.0" force-response-1.0
    BrowserMatch "JDK/1\.0" force-response-1.0

</IfModule>
# End of browser customization directives

#
# Allow server status reports, with the URL of http://servername/server-status
# Change the "localhost" to match your domain to enable.
#
#<Location /server-status>
#    SetHandler server-status
#    Order deny,allow
#    Deny from all
#    Allow from localhost
#</Location>

#
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the "localhost" to match your domain to enable.
#
#<Location /server-info>
#    SetHandler server-info
#    Order deny,allow
#    Deny from all
#    Allow from localhost
#</Location>

#
# There have been reports of people trying to abuse an old bug from pre-1.1
# days.  This bug involved a CGI script distributed as a part of Apache.
# By uncommenting these lines you can redirect these attacks to a logging
# script on phf.apache.org.  Or, you can record them yourself, using the script
# support/phf_abuse_log.cgi.
#
#<Location /cgi-bin/phf*>
#    Deny from all
#    ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
#</Location>

### Section 3: Virtual Hosts
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at <URL:http://www.apache.org/docs/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
#NameVirtualHost *:83

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
#<VirtualHost *:83>
#    ServerAdmin webmaster@dummy-host.example.com
#    DocumentRoot /www/docs/dummy-host.example.com
#    ServerName dummy-host.example.com
#    ErrorLog logs/dummy-host.example.com-error_log
#    CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost>

分享到:
评论

相关推荐

    环境流体力学:河流流动模拟.zip

    光电材料仿真,电子仿真等;从入门到精通教程;含代码案例解析。

    C#实现Stewart六自由度平台反解算法及其应用

    内容概要:本文详细介绍了如何使用C#实现Stewart六自由度平台的逆解算法。首先定义了平台的基本结构,包括上下平台的半径、安装角度以及舵机零位偏移等参数。接着,通过欧拉角转换为旋转矩阵的方式实现了姿态转换,并在此基础上计算各个支腿的长度。文中还特别强调了一些常见的陷阱,如角度单位一致性、安装方向匹配、零位校准和数值稳定性等问题。此外,提供了具体的测试用例用于验证算法的正确性和性能。 适合人群:具有一定C#编程基础并对机械臂控制、飞行模拟器或手术机器人等领域感兴趣的开发者和技术人员。 使用场景及目标:适用于需要精确控制六自由度平台的应用场合,如飞行模拟器、手术机器人等。主要目的是通过数学模型将平台的姿态转换为具体的操作指令,从而实现精准定位与操控。 其他说明:文中不仅给出了完整的代码实现,还分享了许多实践经验,帮助读者更好地理解和应用该算法。同时提醒开发者在实际项目中需要注意的一些关键点,如行程限制检查、运动学奇异性检测等。

    夸克网盘批量处理助手,同步更新保存分享链接文件,增量更新文件,批量重命名文件夹,文件名称关键词替换

    夸克网盘批量处理助手,同步更新保存分享链接文件,增量更新文件,批量重命名文件夹,文件名称关键词替换

    XML.md

    XML.md

    MATLAB实现光纤光栅均匀与非均匀应变仿真及其在光学传感的应用

    内容概要:本文详细介绍了利用MATLAB进行光纤光栅的均匀应变和非均匀应变仿真的方法。文中提供了具体的代码实例,解释了如何通过调整光栅的基本参数如中心波长、光栅长度、有效折射率等,以及引入应变系数和应变分布函数,分别计算均匀应变和非均匀应变下光纤光栅的反射率,并展示了相应的反射率曲线图。此外,还讨论了这两种应变模式对光栅反射谱的不同影响,强调了非均匀应变可能导致的光谱畸变现象。 适用人群:对光纤光栅仿真感兴趣的研究人员和技术爱好者,尤其是那些希望通过MATLAB进行光器件设计和测试的人群。 使用场景及目标:①用于科研项目中光纤光栅特性的研究;②辅助工程师在实际工程项目中评估光纤光栅传感器的表现;③帮助学生理解光纤光栅的工作机制和应变对其性能的影响。 其他说明:文章不仅提供了详细的代码实现步骤,还分享了一些调试技巧和注意事项,有助于读者更好地理解和应用所介绍的技术。

    计算机网络基于b站的学习笔记

    计算机网络概念,计算机网络,互联网,互连网的区别;计算机网络的组成、功能;三种交换技术;计算机网络的性能指标;以及计算机网络的分类

    基于Simulink的ABS仿真模型及其PID控制策略的应用与优化

    内容概要:本文详细介绍了如何使用Simulink搭建防抱死制动系统(ABS)的仿真模型,并应用PID控制策略进行仿真分析。首先,文章解释了ABS系统的重要性和工作原理,然后逐步讲解了如何在Simulink中构建车轮动力学模块、制动压力模块等关键组件。接下来,文章深入探讨了PID控制策略的具体实现方法,包括PID参数的选择和调整技巧。通过多次仿真实验,展示了不同PID参数对ABS系统性能的影响,并提出了优化方案,如变增益策略和积分分离策略。最后,文章分享了一些实用的经验和技巧,如处理低速时的数值稳定性、应对路面突变等情况。 适合人群:对汽车工程、控制系统设计感兴趣的工程师和技术爱好者,尤其是那些希望深入了解ABS系统和PID控制策略的人群。 使用场景及目标:适用于希望在虚拟环境中研究和优化ABS系统性能的研究人员和工程师。主要目标是提高ABS系统的制动性能和安全性,确保在各种工况下都能保持最佳的制动效果。 其他说明:文中不仅提供了理论知识,还包括了大量的实际案例和代码片段,帮助读者更好地理解和应用所学内容。此外,作者还分享了许多实践经验,如如何处理仿真中的常见问题和优化策略。

    独子棋demo.rar

    独子棋demo.rar

    基于Maxwell-Simplorer的永磁同步电机SVPWM控制联合仿真研究

    内容概要:本文详细介绍了如何利用Maxwell和Simplorer进行矢量联合仿真,结合SVPWM(空间矢量脉宽调制)算法实现对永磁同步电机的精确控制。文章首先解释了SVPWM的基本原理及其Python实现,接着阐述了在Maxwell中建立电机模型并设置参数的具体步骤,以及在Simplorer中搭建控制系统的方法。文中还讨论了仿真过程中如何调整控制器参数以优化系统性能,并展示了如何通过分析仿真结果来评估控制效果。此外,文章探讨了将该方法应用于其他类型电机的可能性,如感应电机和开关磁阻电机。 适合人群:从事电机控制领域的研究人员和技术人员,尤其是对永磁同步电机和SVPWM算法感兴趣的读者。 使用场景及目标:适用于需要深入了解永磁同步电机控制原理的研究人员,帮助他们掌握Maxwell和Simplorer联合仿真的具体操作流程,提高对电机控制系统的理解和优化能力。 其他说明:文章不仅提供了详细的理论讲解,还附有大量代码片段和实践经验,有助于读者更好地理解和应用相关技术。同时,文章强调了实践中可能遇到的问题及解决方法,使读者能够在实际工作中避免常见错误。

    【太阳能电池片图像处理】基于边缘检测与频域滤波的预处理系统设计:图像倾斜校正及栅格去除(论文复现或解答,含详细代码及解释)

    内容概要:本文详细介绍了太阳能电池片在线颜色分选系统的图像预处理方法。针对采集的原始图像中存在的传送带背景和随机倾斜等问题,提出了完整的预处理流程。主要包括:倾斜校正(通过边缘检测和霍夫变换)、去除栅格干扰(频域滤波和形态学操作),以及对多种边缘检测算子(如Roberts、Sobel、Prewitt、Canny和LOG)的比较与分析。此外,还探讨了不同直线检测方法(如Radon变换、Hough变换及其改进版本)的应用,并优化了整个预处理流程,确保后续的颜色特征提取和分类准确性。 适用人群:从事计算机视觉、图像处理领域的研究人员和技术人员,特别是专注于工业自动化检测设备开发的工程师。 使用场景及目标:①实现太阳能电池片图像的倾斜校正,确保图像水平放置;②有效去除电池片表面栅线对颜色分析的影响;③为后续的颜色特征提取和分类提供高质量的输入数据;④比较不同边缘检测算子的效果,选择最适合特定任务的算子;⑤评估各种直线检测方法的性能,选择最优方案应用于实际生产环境中。 其他说明:文中不仅提供了详细的理论解释,还给出了具体的Python代码实现,帮助读者更好地理解和实践相关技术。同时,针对实际应用中的常见问题,如参数调优、光照一致性和异常处理等方面也给出了相应的建议。最后,通过一系列实验验证了所提方法的有效性,并提出了一些性能优化的方向。

    Comsol锂离子电池仿真:电化学-热耦合模型与多物理场分析助力电池热管理

    内容概要:本文详细介绍了利用Comsol进行锂离子电池仿真的技术和应用,特别是在电化学-热耦合模型和多物理场分析方面。文章首先阐述了电化学-热耦合模型在充放电循环中的应用,通过MATLAB伪代码展示了如何定义电池几何形状、材料属性、边界条件以及耦合电化学和热传递过程。接下来讨论了液冷仿真与电池热管理模型,通过Python伪代码解释了液冷通道的构建、流体属性的设置及其流动与热传递的求解。此外,文章还比较了锂电池产热模型下风冷和液冷的不同效果,并强调了产热计算的重要性。最后,文章分享了一些实用的经验和技术细节,如处理高倍率充电时的浓度极化、选择合适的湍流模型、刀片电池的建模技巧等。 适合人群:从事锂离子电池研究和开发的科研人员、工程师及相关领域的学生。 使用场景及目标:①理解和优化锂离子电池的热管理机制;②评估不同冷却方式(如风冷、液冷)的效果;③提高电池系统的性能和安全性。 其他说明:文中不仅提供了详细的理论背景和技术实现步骤,还分享了许多实践经验,有助于读者更好地掌握Comsol在锂离子电池仿真中的应用。

    智能驾驶领域AEB系统的安全距离与TTC切换优化算法及其应用场景

    内容概要:本文探讨了自动紧急制动系统(AEB)中安全距离与时间头时距(TTC)的优化方法。首先介绍了AEB系统的基本原理,包括安全距离和TTC的定义及计算方式。接着提出了基于机器学习的动态调整机制,通过分析历史驾驶数据,训练回归模型预测最优安全距离,并设计了基于规则的智能切换机制,根据车速选择合适的评估标准。此外,通过仿真测试验证了改进算法的有效性,展示了其在低速跟车、高速变道等场景中的优越表现。最后,讨论了联合仿真中的挑战,如多物理场耦合与时序同步问题,并提供了相应的解决方案。 适合人群:从事智能驾驶技术研发的专业人士,尤其是对AEB系统有研究兴趣的工程师和技术爱好者。 使用场景及目标:适用于希望深入了解AEB系统工作原理及优化方法的研发团队。目标是通过改进现有算法,提高AEB系统在各种驾驶场景下的鲁棒性和安全性。 其他说明:文中提到的技术细节和代码片段有助于读者更好地理解和实现相关算法。同时指出了现有研究存在的局限性,为进一步探索提供了方向。

    数据结构.md

    数据结构.md

    格式化输出.md

    格式化输出.md

    三相不平衡电网下模块化多电平变流器(MMC)的先进控制策略及其实现

    内容概要:本文详细探讨了在三相不平衡电网条件下,模块化多电平变流器(MMC)的多种控制策略及其具体实现方法。主要内容包括:利用双二阶广义积分器(DSOGI)进行正负序分离控制,通过PI控制器实现零负环流抑制,以及采用谐振控制器抑制二倍频功率波动。此外,文中还介绍了不同控制模式之间的动态切换逻辑,确保系统在各种工况下的稳定性和高效性。文章提供了详细的MATLAB、Python和Verilog代码片段,展示了各个控制环节的具体实现。 适合人群:从事电力电子、电力系统自动化领域的研究人员和技术人员,尤其是对MMC控制策略感兴趣的工程师。 使用场景及目标:适用于需要解决三相不平衡电网问题的研究项目和工业应用场景。主要目标是在电压跌落等恶劣工况下,确保MMC系统的稳定性和平滑运行,提高系统的鲁棒性和效率。 其他说明:文中引用了多篇相关领域的权威文献,为读者提供了进一步深入研究的方向。同时,作者强调了理论仿真与实际调试之间的差距,提醒读者在实验过程中需要注意的安全事项。

    Python编程与PyQt GUI应用开发

    本书是关于Python编程语言和使用PyQt框架开发图形用户界面(GUI)应用的全面指南。首先介绍了Python的基础知识,包括安装、与Python交互、编写第一个程序、数据类型、基本元素、注释、续行和打印等。随后,深入探讨了Python的算术运算、位运算、复数、决策、逻辑运算符、循环等核心概念。接着,书中详细讲解了序列(包括字符串、列表、元组和集合)、函数和模块、类(包括类声明、方法、继承、垃圾回收、运算符重载和描述符)、文件处理以及异常处理。最后,作者重点介绍了PyQt框架,包括安装、窗口和对话框的创建、使用代码和Qt Designer创建GUI应用程序、基础控件、事件处理、高级控件(如LCD时钟、日历、组合框、表格、Web页面和图形显示)、菜单和工具栏的使用。本书适合希望学习Python编程和GUI开发的读者。

    espidf启动流程基于esp32c3

    espidf启动流程

    煤矿瓦斯气驱技术中二氧化碳与氮气应用的Python自动化解决方案

    内容概要:本文详细介绍了利用Python进行煤矿瓦斯气驱过程中二氧化碳和氮气的应用方法和技术细节。首先展示了如何通过Python脚本处理气驱压力监测数据并绘制对比图,接着讲解了注气速率控制的PID算法实现及其注意事项。文中还涉及裂隙气体扩散模拟、湿度对氮气驱替的影响以及基于状态机的注气控制系统设计。此外,提供了实时气体浓度监控、数据滤波、阈值报警等功能的具体实现方式,并强调了数据可视化的应用价值。最后讨论了注气孔布置优化和注气压力控制的实际操作要点。 适合人群:从事煤矿开采及相关领域的技术人员、工程师,尤其是具有一定编程基础并对自动化控制感兴趣的从业者。 使用场景及目标:适用于煤矿瓦斯气驱项目的规划、实施与维护阶段,旨在提高瓦斯抽采效率,确保安全生产,同时减少人为因素导致的操作失误。通过学习本文提供的代码示例和技术方案,读者能够掌握如何运用Python解决实际工程问题的方法。 其他说明:文中提到的所有代码均为简化版本,用于解释相关概念和技术原理,在实际项目中可能需要进一步完善和优化。对于希望深入了解该领域的读者而言,本文不仅提供了实用的技术指导,也为后续研究奠定了良好的基础。

    CAML官方作者的版本有很多bug、模型无法下载,并且没做做优化等问题,所以基本上大多数人是无法使用的 而此资源代码,是本人包括在源代码理解上咨询原作者、不断调试试验等进行代码层开发改造的成果

    CAML(Context-Aware Meta-Learning)是一种基于元学习的少样本学习算法。CAML通过引入上下文感知的机制,实现小样本图像的识别分类。基本上是n-way k-shot的最佳效果模型。 此资源为源码包,是本人在攻克小样本学习问题上,花了一个月进行改进与分析后的代码,安装环境后,可以直接运行caml_infer_main.py。 参考关联文章:https://blog.csdn.net/A15216110998/article/details/144600715?spm=1011.2415.3001.5331 1.实现输入单张图片进行推理,输出类别和概率。 2.模型下载通过本地文件进行加载,内带有模型文件下载链接。 3.不再随机抽样,启动时加载指定的支持集,运行时输入一张图片作为查询集。 4.可任意指定支持集的位置、任意指定模型所在的位置。 5.样本特征编码部分和逻辑修改,源码bug修改。

Global site tag (gtag.js) - Google Analytics