Displaying 7 results from an estimated 7 matches for "lws".
Did you mean:
lds
2009 Sep 17
3
generating unordered combinations
Hi,
I am trying to generate all unordered combinations of a set of
numbers / characters, and I can only find a (very) clumsy way of doing
this using expand.grid. For example, all unordered combinations of
the numbers 0, 1, 2 are:
0, 0, 0
0, 0, 1
0, 0, 2
0, 1, 1
0, 1, 2
0, 2, 2
1, 1, 1
1, 1, 2
1, 2, 2
2, 2, 2
(I have not included, for example, 1, 0, 0, since it is equivalent to
0, 0, 1).
I have
2011 Jul 10
0
Release for CentOS-6.0 i386 and x86_64
...from
the livemedia.
+++++++++++++++++++++++
Minimal Install CD
We have also created a minimal install CD, that would bring up a base
machine with just enough content to have a usable platform. This CD
image will be released in the next few days.
+++++++++++++++++++++++
The LightWeightServer (LWS) CD
In order to bring back the CentOS-4 Server CD style single iso image, we
are creating a LWS varient of the main distro. Details for this will be
posted in the next few days with release happening after the live media
and the minimal cd editions.
+++++++++++++++++++++++
Downloading CentOS-6...
2011 Jul 11
0
CentOS-announce Digest, Vol 77, Issue 4
...from
the livemedia.
+++++++++++++++++++++++
Minimal Install CD
We have also created a minimal install CD, that would bring up a base
machine with just enough content to have a usable platform. This CD
image will be released in the next few days.
+++++++++++++++++++++++
The LightWeightServer (LWS) CD
In order to bring back the CentOS-4 Server CD style single iso image, we
are creating a LWS varient of the main distro. Details for this will be
posted in the next few days with release happening after the live media
and the minimal cd editions.
+++++++++++++++++++++++
Downloading CentOS-6...
2009 Nov 29
3
Parsing custom SIP headers
...erisk that
parses custom "name-addr"-style SIP headers for me?
If I wanted to do it right the syntax
name-addr *(SEMI generic-param)
is quite complex to parse in the dialplan using nothing but CUT().
It's so easy to make false assumtions about angle brackets (< >),
whitespace (LWS), quotes (") around the display-name, character
escaping etc. All of the applications of CUT() I have seen are
way too simplistic.
Example of how it could work:
Set(addr=${SIP_PARSE_HEADER(${SIP_HEADER(P-Asserted-Identity)},addr-spec)});
Interesting parts include:
name-addr, display-name, ad...
2003 Jun 25
0
[patch] Basic HTTP Proxy Authentication
...is patch in the
rsync 2.5.6 package.
(Note: Please CC to me, as I'm not subscribed to the list)
[0] RFC 2617 (HTTP Autentication) defines the userid field as TEXT[1]
excluding ":".
[1] RFC 2616 (HTTP) defines TEXT as any OCTECT (any 8-bit sequence of
data) except CLTs, but including LWS.
[2] RFC 2138 (Radius) defines a field as "name@fqdn"
--
Alvaro Figueroa
2004 Aug 06
1
details of HTTP Basic auth for icecast2
...Modified ; Section 14.29
| extension-header
extension-header = message-header
an in section 4.2, Message Headers:
message-header = field-name ":" [ field-value ]
field-name = token
field-value = *( field-content | LWS )
field-content = <the OCTETs making up the field-value
and consisting of either *TEXT or combinations
of token, separators, and quoted-string>
(missing definitions can be found in section 2.2, Basic rules)
the spec says that all th...
2004 Aug 06
3
details of HTTP Basic auth for icecast2
Hi,
A question for the HTTP Basic auth for icecast2: what is the username to
use when doing such authentication. The related line in the login is:
Authorization: Basic <base64 encoded string>
where the <base64 encoded string> in its original form is:
username:password
now, what username is used? in the config file for the icecast2 server,
one can only set the password (except