Thứ Hai, 12 tháng 11, 2012

Upgrading apache to 2.4 from 2.2

Chuyển từ apache 2.2  lên apache 2.4 sẽ phải thay đổi 1 số cấu hình

Link: http://httpd.apache.org/docs/2.4/upgrading.html

Sau đây là trích dẫn nội dung:

Upgrading to 2.4 from 2.2

Available Languages:  en  |  fr 
In order to assist folks upgrading, we maintain a document describing information critical to existing Apache HTTP Server users. These are intended to be brief notes, and you should be able to find more information in either the New Features document, or in the src/CHANGES file. Application and module developers can find a summary of API changes in the API updates overview.
This document describes changes in server behavior that might require you to change your configuration or how you use the server in order to continue using 2.4 as you are currently using 2.2. To take advantage of new features in 2.4, see the New Features document.
This document describes only the changes from 2.2 to 2.4. If you are upgrading from version 2.0, you should also consult the 2.0 to 2.2 upgrading document.

 Compile-Time Configuration Changes

The compilation process is very similar to the one used in version 2.2. Your old configure command line (as found in build/config.nice in the installed server directory) can be used in most cases. There are some changes in the default settings. Some details of changes:
  • These modules have been removed: mod_authn_default, mod_authz_default, mod_mem_cache. If you were using mod_mem_cache in 2.2, look at mod_cache_disk in 2.4.
  • All load balancing implementations have been moved to individual, self-contained mod_proxy submodules, e.g. mod_lbmethod_bybusyness. You might need to build and load any of these that your configuration uses.
  • Platform support has been removed for BeOS, TPF, and even older platforms such as A/UX, Next, and Tandem. These were believed to be broken anyway.
  • configure: dynamic modules (DSO) are built by default
  • configure: By default, only a basic set of modules is loaded. The other LoadModule directives are commented out.
  • configure: the "most" module set gets built by default
  • configure: the "reallyall" module set adds developer modules to the "all" set
top

Run-Time Configuration Changes

There have been significant changes in authorization configuration, and other minor configuration changes, that could require changes to your 2.2 configuration files before using them for 2.4.

Authorization

Any configuration file that uses authorization will likely need changes.
You should review the Authentication, Authorization and Access Control Howto, especially the section Beyond just authorization which explains the new mechanisms for controlling the order in which the authorization directives are applied.
Directives that control how authorization modules respond when they don't match the authenticated user have been removed: This includes AuthzLDAPAuthoritative, AuthzDBDAuthoritative, AuthzDBMAuthoritative, AuthzGroupFileAuthoritative, AuthzUserAuthoritative, and AuthzOwnerAuthoritative. These directives have been replaced by the more expressive RequireAny, RequireNone, and RequireAll.

Access control

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy.
In 2.4, such access control is done in the same way as other authorization checks, using the new module mod_authz_host. The old access control idioms should be replaced by the new authentication mechanisms, although for compatibility with old configurations, the new module mod_access_compat is provided.
Here are some examples of old and new ways to do the same access control.
In this example, all requests are denied.

2.2 configuration:

Order deny,allow
Deny from all

2.4 configuration:

Require all denied
In this example, all requests are allowed.

2.2 configuration:

Order allow,deny
Allow from all

2.4 configuration:

Require all granted
In the following example, all hosts in the example.org domain are allowed access; all other hosts are denied access.

2.2 configuration:

Order Deny,Allow
Deny from all
Allow from example.org

2.4 configuration:

Require host example.org

Other configuration changes

Some other small adjustments may be necessary for particular configurations as discussed below.
  • MaxRequestsPerChild has been renamed to MaxConnectionsPerChild, describes more accurately what it does. The old name is still supported.
  • MaxClients has been renamed to MaxRequestWorkers, which describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported.
  • The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none. You need to use other configuration settings to replace it in 2.4.
  • EnableSendfile now defaults to Off.
  • FileETag now defaults to "MTime Size" (without INode).
  • mod_log_config: ${cookie}C matches whole cookie names. Previously any substring would match.
  • mod_dav_fs: The format of the DavLockDB file has changed for systems with inodes. The old DavLockDB file must be deleted on upgrade.
  • KeepAlive only accepts values of On or Off. Previously, any value other than "Off" or "0" was treated as "On".
  • Directives AcceptMutex, LockFile, RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine if they can just be deleted or will need to be replaced using Mutex.
  • mod_cache: CacheIgnoreURLSessionIdentifiers now does an exact match against the query string instead of a partial match. If your configuration was using partial strings, e.g. using sessionid to match /someapplication/image.gif;jsessionid=123456789, then you will need to change to the full string jsessionid.
  • mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts.
  • mod_filter: FilterProvider syntax has changed and now uses a boolean expression to determine if a filter is applied.
  • mod_include:
    • The #if expr element now uses the new expression parser. The old syntax can be restored with the new directive SSILegacyExprParser.
    • An SSI* config directive in directory scope no longer causes all other per-directory SSI* directives to be reset to their default values.
  • mod_charset_lite: The DebugLevel option has been removed in favour of per-module LogLevel configuration.
  • mod_ext_filter: The DebugLevel option has been removed in favour of per-module LogLevel configuration.
  • mod_ssl: CRL based revocation checking now needs to be explicitly configured through SSLCARevocationCheck.
  • mod_substitute: The maximum line length is now limited to 1MB.
  • mod_reqtimeout: If the module is loaded, it will now set some default timeouts.
top

Misc Changes

  • mod_autoindex: will now extract titles and display descriptions for .xhtml files, which were previously ignored.
  • mod_ssl: The default format of the *_DN variables has changed. The old format can still be used with the new LegacyDNStringFormat argument to SSLOptions. The SSLv2 protocol is no longer supported. SSLProxyCheckPeerCN and SSLProxyCheckPeerExpire now default to On, causing proxy requests to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway)
  • htpasswd now uses MD5 hash by default on all platforms.
  • The NameVirtualHost directive no longer has any effect, other than to emit a warning. Any address/port combination appearing in multiple virtual hosts is implicitly treated as a name-based virtual host.
  • mod_deflate will now skip compression if it knows that the size overhead added by the compression is larger than the data to be compressed.
  • Multi-language error documents from 2.2.x may not work unless they are adjusted to the new syntax of mod_include's #if expr= element or the directive SSILegacyExprParser is enabled for the directory containing the error documents.
  • The functionality provided by mod_authn_alias in previous versions (i.e., the AuthnProviderAlias directive) has been moved into mod_authn_core.
top

Third Party Modules

All modules must be recompiled for 2.4 before being loaded.
Many third-party modules designed for version 2.2 will otherwise work unchanged with the Apache HTTP Server version 2.4. Some will require changes; see the API update overview.
top

Common problems when upgrading

  • Startup errors:
    • Invalid command 'User', perhaps misspelled or defined by a module not included in the server configuration - load module mod_unixd
    • Invalid command 'Require', perhaps misspelled or defined by a module not included in the server configuration, or Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration - load module mod_access_compat, or update configuration to 2.4 authorization directives.
    • Ignoring deprecated use of DefaultType in line NN of /path/to/httpd.conf - remove DefaultType and replace with other configuration settings.
  • Errors serving requests:
    • configuration error: couldn't check user: /path - load module mod_authn_core.

Thứ Ba, 6 tháng 11, 2012

HTML ISO-8859-1 Reference

Các ký tự đặc biệt trong HTML:

Link tham khảo: http://www.w3schools.com/tags/ref_entities.asp

Thứ Tư, 10 tháng 10, 2012

Đăng ký DV 3G Viettel

Đăng ký DV 3G Viettel

Đăng ký chuyển đổi sang mạng 3G (Áp dụng với thuê bao trả trước và trả sau)
Có 2 cách:
Cách 1: Khách hàng đăng ký sử dụng 3G tại các cửa hàng Viettel trên toàn quốc.
Cách 2: Khách hàng tự đăng ký thông qua 3 bước đơn giản:
Bước 1: Đăng ký chuyển đổi mạng 3G
Khách hàng soạn tin nhắn nội dung: 3G ON gửi 161
Cước phí duy trì dịch vụ: 10.000đ/tháng
Sau khi chuyển sang 3G, khách hàng được giữ nguyên tính chất gói cước 2G cũ và bổ sung tính năng Video call, Mobile Internet.
Bước 2: Chuyển băng tần cho máy từ GSM sang UMTS băng tần 1900 – 2100 Mhz.
Menu >> Settings >>Phone >>Network >> Network Mode >> chọn UMTS


Bonus:  Dang ky Mimax: mimax gui 191

Thứ Ba, 2 tháng 10, 2012

Fix lỗi SQLSTATE[HY000]: General error: 145 Table xxx is marked as crashed and should be repaired

Hôm nay sau 1 hồi start, stop rồi kill MySQL thì gặp phải lỗi:

SQLSTATE[HY000]: General error: 145 Table xxx is marked as crashed and should be repaired

Cách fix:
 
REPAIR TABLE tablename

Thứ Sáu, 24 tháng 8, 2012

Kinh nghiệm làm việc với Nagios



Plugin NRPE: http://exchange.nagios.org/directory/Addons/Monitoring-Agents/NRPE--2D-Nagios-Remote-Plugin-Executor/details

Lỗi gặp phải khi cài đặt:
- Khi configure NRPE thì có lỗi không tìm được thư viện ssl
- Cách fix: 
+ apt-get install libcurl3-openssl-dev
+ ./configure --with-ssl=/usr/bin/openssl --with-ssl-lib=/usr/lib

Thứ Sáu, 17 tháng 8, 2012

Thư mục php-cli

Tìm mãi mới ra. Trong: /usr/bin/php

Trong đó gồm cả thập cẩm mấy thứ: php-ize, php-config....

Thứ Năm, 16 tháng 8, 2012

Regular Expression Wiki

In the BRE syntax, most characters are treated as literals — they match only themselves (e.g., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.
Metacharacter Description
. Matches any single character (many applications exclude newlines, and exactly which characters are considered newlines is flavor-, character-encoding-, and platform-specific, but it is safe to assume that the line feed character is included). Within POSIX bracket expressions, the dot character matches a literal dot. For example, a.c matches "abc", etc., but [a.c] matches only "a", ".", or "c".
[ ] A bracket expression. Matches a single character that is contained within the brackets. For example, [abc] matches "a", "b", or "c". [a-z] specifies a range which matches any lowercase letter from "a" to "z". These forms can be mixed: [abcx-z] matches "a", "b", "c", "x", "y", or "z", as does [a-cx-z]. The - character is treated as a literal character if it is the last or the first (after the ^) character within the brackets: [abc-], [-abc]. Note that backslash escapes are not allowed. The ] character can be included in a bracket expression if it is the first (after the ^) character: []abc].
[^ ] Matches a single character that is not contained within the brackets. For example, [^abc] matches any character other than "a", "b", or "c". [^a-z] matches any single character that is not a lowercase letter from "a" to "z". Likewise, literal characters and ranges can be mixed.
^ Matches the starting position within the string. In line-based tools, it matches the starting position of any line.
$ Matches the ending position of the string or the position just before a string-ending newline. In line-based tools, it matches the ending position of any line.
BRE: \( \)
ERE: ( )
Defines a marked subexpression. The string matched within the parentheses can be recalled later (see the next entry, \n). A marked subexpression is also called a block or capturing group.
\n Matches what the nth marked subexpression matched, where n is a digit from 1 to 9. This construct is theoretically irregular and was not adopted in the POSIX ERE syntax. Some tools allow referencing more than nine capturing groups.
* Matches the preceding element zero or more times. For example, ab*c matches "ac", "abc", "abbbc", etc. [xyz]* matches "", "x", "y", "z", "zx", "zyx", "xyzzy", and so on. \(ab\)* matches "", "ab", "abab", "ababab", and so on.
BRE: \{m,n\}
ERE: {m,n}
Matches the preceding element at least m and not more than n times. For example, a\{3,5\} matches only "aaa", "aaaa", and "aaaaa". This is not found in a few older instances of regular expressions.
Examples:
  • .at matches any three-character string ending with "at", including "hat", "cat", and "bat".
  • [hc]at matches "hat" and "cat".
  • [^b]at matches all strings matched by .at except "bat".
  • ^[hc]at matches "hat" and "cat", but only at the beginning of the string or line.
  • [hc]at$ matches "hat" and "cat", but only at the end of the string or line.
  • \[.\] matches any single character surrounded by "[" and "]" since the brackets are escaped, for example: "[a]" and "[b]".

Lỗi khi so sánh chuỗi trong PHP

Mọi hôm lười toàn so sánh kiểu ==

Hôm nay gặp lỗi so sánh 2 chuỗi: 01235000000000000000000000000000001235 &  01235000000000000000000000000000001234  cho kết quả bằng nhau
Giải pháp: chuyển sang strcmp

Sẽ cập nhật sau sự khác nhau giữa strcmp  vs  '=='

Thứ Tư, 6 tháng 6, 2012

[Symfony2] Chi tiết luồng xử lý form

There are two types of events:
DataEvent - read-only access to the form data. 'Pre' and 'Post' events are read-only.
FilterDataEvent - event that allows the form data to be modified.
form.pre_bind DataEvent triggered before data is bound to the form. Triggered by Symfony\Component\Form\Form::bind()
form.post_bind DataEvent triggered after data is bound to the form. Triggered by Symfony\Component\Form\Form::bind()
form.pre_set_data DataEvent triggered before fields are filled with default data. Triggered by Symfony\Component\Form\Form::setData()
form.post_set_data DataEvent triggered after fields are filled with default data. Triggered by Symfony\Component\Form\Form::setData()
form.bind_client_data FilterDataEvent triggered before data is bound to the form. Triggered by Symfony\Component\Form\Form::bind()
form.bind_norm_data FilterDataEvent triggered after data has been normalized. Triggered by Symfony\Component\Form\Form::bind(). See Symfony\Component\Form\Extension\Core\EventListener\FixUrlProtocolListener (added by the UrlType for an example)
form.set_data FilterDataEvent triggered while default data is being bound. Triggered by Symfony\Component\Form\Form::setData()
I'd recommend poking around the Form class itself to get a better feel for when these events are triggered, and how you can use them.

Thứ Ba, 5 tháng 6, 2012

[Symfony2] Lỗi khi dùng Sonata Admin với Oracle

Lỗi không hiểu ngày tháng:
1. Chỉnh sửa Session của Oracle (có thể ko cần)
ALTER SESSION set NLS_DATE_FORMAT = "YYYY-MM-DD HH24:MI:SS";
2. Thêm vào cấu hình config.yml:
services:
   my.listener:
      class: Doctrine\DBAL\Event\Listeners\OracleSessionInit
      tags:
          - { name: doctrine.event_listener, event: postConnect }
3. Lỗi set null ID: bổ sung trigger cho Oracle