On Fri, Jun 12, 2015 at 07:38:19PM +1200, Steve Holdoway wrote:
> On 12/06/15 18:59, Francis Daly wrote:
> >On Fri, Jun 12, 2015 at 01:50:15PM +1200, steve wrote:
Hi there,
> >>$ curl -I http://backend.right.bike/images/models/Lapierre/Overvolt\ FS.png
> >>HTTP/1.1 200 OK
> >>$ curl -I http://bac
Hi,
On 12/06/15 18:59, Francis Daly wrote:
On Fri, Jun 12, 2015 at 01:50:15PM +1200, steve wrote:
Hi there,
I'm tryiong to make some sense out of this and am left a bit cold!
What could cause this:
Both requests are invalid - "space" may not appear in a url. Encode it
as %20 and things will
On Fri, Jun 12, 2015 at 01:50:15PM +1200, steve wrote:
Hi there,
> I'm tryiong to make some sense out of this and am left a bit cold!
> What could cause this:
Both requests are invalid - "space" may not appear in a url. Encode it
as %20 and things will work.
nginx happens to try one form of "dw
Hello
Can you try something command like the ones at
http://unix.stackexchange.com/questions/2182/identifying-files-with-special-characters-in-its-name-in-a-terminal
to see if you have special chars in some of the filenames?
On Fri, Jun 12, 2015 at 3:50 AM, steve wrote:
> I'm tryiong to make
Hmm...
On 12/06/15 14:31, steve wrote:
A bit more into...
On 12/06/15 14:15, Miguel Clara wrote:
BTW, I test a few more URLS, and all others give 404, but anything
with "http://backend.right.bike/images/models/Lapierre/Overvolt\ H***"
fails with 400
not that only "Overvolt\ H" and "Overvolt H
A bit more into...
On 12/06/15 14:15, Miguel Clara wrote:
BTW, I test a few more URLS, and all others give 404, but anything
with "http://backend.right.bike/images/models/Lapierre/Overvolt\ H***"
fails with 400
not that only "Overvolt\ H" and "Overvolt H fails not "Overvolt\ h"
or "Overvolt h"
BTW, I test a few more URLS, and all others give 404, but anything
with "http://backend.right.bike/images/models/Lapierre/Overvolt\ H***"
fails with 400
not that only "Overvolt\ H" and "Overvolt H fails not "Overvolt\ h"
or "Overvolt h"
I just have no clue why, maybe something in the config
Melh
On Fri, Jun 12, 2015 at 3:00 AM, steve wrote:
> Aargh!
>
>
> On 12/06/15 13:56, Miguel Clara wrote:
>>
>> Interesting I tried at my side got the same results but it does work like
>> this:
>>
>> curl -I
>> "http://backend.right.bike/images/models/Lapierre/Overvolt%20HT.png";
>> HTTP/1.1 200 OK
>
Aargh!
On 12/06/15 13:56, Miguel Clara wrote:
Interesting I tried at my side got the same results but it does work like this:
curl -I "http://backend.right.bike/images/models/Lapierre/Overvolt%20HT.png";
HTTP/1.1 200 OK
Server: nginx/1.9.1
Date: Fri, 12 Jun 2015 01:55:27 GMT
Content-Type: ima
Interesting I tried at my side got the same results but it does work like this:
curl -I "http://backend.right.bike/images/models/Lapierre/Overvolt%20HT.png";
HTTP/1.1 200 OK
Server: nginx/1.9.1
Date: Fri, 12 Jun 2015 01:55:27 GMT
Content-Type: image/png
Content-Length: 318335
Last-Modified: Thu,
Just a quick addition... I've tried it from this office, which is IPv4,
and from IPv6 enabled locations. This makes no difference.
On 12/06/15 13:50, steve wrote:
I'm tryiong to make some sense out of this and am left a bit cold!
What could cause this:
( I've left out any attempt at anonymis
I'm tryiong to make some sense out of this and am left a bit cold! What
could cause this:
( I've left out any attempt at anonymising in case I hide something )
From the docroot...
$ ls -l images/models/Lapierre/Overvolt*
-rw-r--r-- 1 right-bike right-bike 342373 Jun 11 20:09
images/models/Lap
12 matches
Mail list logo