similar to: [PATCH] fish: add small documentation bit about format of URIs (RHBZ#1450325)

According to RFC 3986, ''['' and '']'' are reserved characters. However, Rails 3.0.7 is not escaping them. This is fixed in master by this commit: https://github.com/rails/rails/commit/52b71c01fd3c8a87152f55129a8cb3234190734a Can this fix be included in 3.0.x ? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails:

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

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) #

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

I just noticed something interesting (or not) about getting to my RoR app on the 2 browsers. I''ve tested it running Webrick or Mongrel_rails and get the same behavior. The app is at http://www.mydomain.com:myport#/app/list Specifying that complete URL works fine in both browsers. However in IE if you just specify www.mydomain.com:myport#/app/list I get page not found. In FF the URL

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 13/11/2020 22:04, PGNet Dev wrote: >> I guess you didn't need to enclose username and password in quotes, i.e. >> >> fts_solr = >> url=https://myuser:my%40pass at solr.example.com:8984/solr/dovecot/ >> use_libfts soft_commit=yes batch_size=250 > > On 11/13/20 12:56 PM, John Fawcett wrote: > >> I guess you didn't need to enclose username and

Hi Ian, CMML is still a draft, so we can change the addressing if required. You're correct, currently something like blah.cmml#fragment points to a clip (or temporal section) of the stream, but blah.cmml#t=12 points to a 12 seconds offset. (same for annodex, i.e. ogg files with skeleton track). For pointing to logical streams inside ogg, I'd really suggest you have a look at

Hi Ian, CMML is still a draft, so we can change the addressing if required. You're correct, currently something like blah.cmml#fragment points to a clip (or temporal section) of the stream, but blah.cmml#t=12 points to a 12 seconds offset. (same for annodex, i.e. ogg files with skeleton track). For pointing to logical streams inside ogg, I'd really suggest you have a look at

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 -U - --run '$nbd' will now >error out rather than

Silvia.Pfeiffer@csiro.au wrote: > Hi Ian, > > CMML is still a draft, so we can change the addressing if required. > You're correct, currently something like > > blah.cmml#fragment > > points to a clip (or temporal section) of the stream, but > > blah.cmml#t=12 > > points to a 12 seconds offset. > > (same for annodex, i.e. ogg files with skeleton

On 13/11/2020 21:32, PGNet Dev wrote: > On 11/13/20 11:37 AM, John Fawcett wrote: >>> still dunno why the 401. :-/ >> >> So I just did a quick check of running dovecot with a standalone >> solr-8.7.0 instance and I'm not seeing any issues. > > +1 > >> I confirm I haven't configured anything for indexer or indexer-worker in >> dovecot, just

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