similar to: URIs including [ and ] are not compliant with RFC3986

Does anybody knows a gem for managing flash messages? I would want to add messages to the flash div in the client. Bootstrap support is a plus. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group,

Mention which format URIs follow, with a small example on escaping special characters. --- fish/guestfish.pod | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/fish/guestfish.pod b/fish/guestfish.pod index c3f684563..1201176e9 100644 --- a/fish/guestfish.pod +++ b/fish/guestfish.pod @@ -1225,6 +1225,16 @@ The equivalent API command would be: ><fs> add /disk protocol:ssh

Hello everyone, I''m new in contributing and i saw in the contributing-guides, that i have to write an email at this list. I hope, that''s the right place for this. If it''s not, i''M really sorry.. ;) Could someone please give me feedback about this lighthouse-ticket?

I believe the implementation of utils::URLencode is non-compliant with RFC 3986, which it claims to implement (http://tools.ietf.org/html/rfc3986). Specifically, its percent encoding uses lowercase letters a-f, which it should use uppercase letters A-F. Here's what URLencode currently produces: library("utils") URLencode("*+,;=:/?", reserved = TRUE) #

I'm not sure whether we want to go with just the first patch (reject nbd:unix:/path but still accept nbd:/path), or squash the two in order to go with the second (reject both abbreviated forms, and require scheme://...). Either way, though, nbdkit -U - --run '$nbd' will now error out rather than inadvertently connect over TCP to localhost:10809 instead of the intended Unix connection

The AF_VSOCK protocol added in Linux 5.6 uses a 32 bit port number. For NBD we map this to simple URIs[1] like nbd+vsock://CID:PORT (where CID is a number that acts a bit like a hostname and PORT is a 32 bit port number). eg: nbd+vsock://1:1000000000/ would be port 10^9 on the loopback address VMADDR_CID_LOCAL (== 1). The problem is that libxml2 arbitrarily limits port numbers to 999,999,999.

On 6/26/19 4:05 AM, Martin Kletzander wrote: > On Tue, Jun 25, 2019 at 09:09:58PM -0500, Eric Blake wrote: >> I'm not sure whether we want to go with just the first patch (reject >> nbd:unix:/path but still accept nbd:/path), or squash the two in order >> to go with the second (reject both abbreviated forms, and require >> scheme://...).  Either way, though, nbdkit

On 10/20/19 6:06 AM, Richard W.M. Jones wrote: > New APIs are added which let you enable or disable features of NBD > URIs, mainly for security reasons. > > tls-psk-file is *disabled* by default for obvious security reasons. > All other features are enabled by default. > --- > @@ -1445,6 +1453,75 @@ C<\"qemu:dirty-bitmap:...\"> for qemu-nbd >

Hello, I've seen that Nuance SIP audio provider supports additional information (parameters and extra headers) in SIP URIs, using the format: sip:user:password@host:port;uri-param1;uri-param2?header1&header2 For example, sip:1234@myserver.com;extra_header=Uui?Uui=Hello Does Asterisk support this format? Is there a way to retrieve the value of these additional headers, and then decide

Hello, I''ve looked at a few autocompleters, and really like Script.aculo.us''. I have two suggestions for making it even better: 1) Make the default HTTP method GET, or at least clearly document how to change it (through the prototype options). This will make it possible for the browser as well as intermediaries to cache the results. 2) Make it easier to control the URIs that

Asterisk Project Security Advisory - AST-2016-004 Product Asterisk Summary Long Contact URIs in REGISTER requests can crash Asterisk Nature of Advisory Remote Crash Susceptibility Remote

FYI: Asterisk puts URIs in messages which violates the SIP spec and can't be accepted by URI parsers: username includes a whitespace. See for example the From header field. Attached is example of an incorrect message and related parts of RFC3261 specification. (Who doesn't want to dig into parser details may want to realize that whitespaces are used as uri delimitors in first request

Move the creation of iscsi URIs away from make_uri, composing them manually: this is needed because libxml assumes colons (':') to separate user and password for the authority part, while with iscsi URIs the separator is percentage ('%'), which would be percent-encoded by libxml. --- src/launch-direct.c | 31 ++++++++++++++++++++++++++++--- 1 file changed, 28 insertions(+), 3

I''m having a problem after changing the deployment for one of my rails apps over to mongrel. I''m getting errors like this: Fri Sep 22 12:15:13 MDT 2006: BAD CLIENT (127.0.0.1): HTTP element REQUEST_URI is longer than the 512 allowed length. I have a few urls in my app that base64 encode a rather complex query into the URI so that it can be bookmarked. These work fine in

So, I thought I'd split off a few discussions from the ongoing discussion of the details of a metadata format. A few other things are needed in support, one of these is a scheme for referring to IDs on Ogg files. Curently there is CMML, you can refer to temporal fragments at the stream level. These may be CMML IDs or time interval queries/fragments as in

Here is a OS X message URI in angled brackets: <message://%3cE1KzXg9-0000Qb-3G at smtp1.mail.ox.ac.uk%3e> Markdown yields: <p><message://%3cE1KzXg9-0000Qb-3G at smtp1.mail.ox.ac.uk%3e></p> Shouldn't it have given instead: <p><a href="message://%3cE1KzXg9-0000Qb-3G at smtp1.mail.ox.ac.uk%3e">message://%3cE1KzXg9-0000Qb-3G at

On Sat, Aug 10, 2019 at 04:50:18PM -0500, Eric Blake wrote: > On 8/10/19 8:02 AM, Richard W.M. Jones wrote: > > +++ b/docs/libnbd.pod > > @@ -364,7 +364,7 @@ when it is available. > > > > To connect to a URI via the high level API, use: > > > > - nbd_connect_uri (nbd, "nbd://example.com/"); > > + nbd_connect_uri (nbd,

This has been giving me a headache for a little while, so I thought I would throw the question out to the list. Imagine there is a database lookup function that takes place that, given a number, returns call routing information. It might be a postgresql lookup, it might be an enum lookup. If I have something like: exten => _.,1,LookUp(${EXTEN}) exten => _.,2,Dial(${RESULT}) Then the

New APIs are added which let you enable or disable features of NBD URIs, mainly for security reasons. tls-psk-file is *disabled* by default for obvious security reasons. All other features are enabled by default. --- generator/generator | 127 +++++++++++++++++++++++++++++++++++++++++++- lib/handle.c | 26 +++++++++ lib/internal.h | 5 ++ lib/uri.c | 31 +++++++++--

My first post here, so a brief intro: I'm somewhat new to Asterisk, but have been working with SIP in depth for about 3 years. I studied Asterisk for about a year and have been experimenting with it hands-on for the past month or so. I've done 6 Asterisk installs in wildly different roles/applications, some of them test systems, others in semi-production, so I know a little bit about