>
> I think that's the only possible error response that you can deliver
> from a Squid ACL. But a deny_info could be useful. Maybe Domas didn't
> get up to the deny_info section in the manual ;)
Would make a good joke, eh?! :)
Domas
___
foundation-l
On 11/12/10 00:07, Austin Hair wrote:
> On Fri, Dec 10, 2010 at 1:49 PM, Domas Mituzas
> wrote:
>>> Like you say, though, it's definitely a technical issue to be
>>> taken up elsewhere.
>>
>> Where you will be told that this is 'working as intended'. &
>> is usually sent in URLs by broken clients
Or rather drop the JS and just put links to static pages in other
languages. A single language is definitely a big step back.
Strainu
2010/12/13 Thomas Dalton :
> On 13 December 2010 12:27, Tim Starling wrote:
>> In principle, it would be possible to have a short error message with
>> a
On 13 December 2010 12:27, Tim Starling wrote:
> In principle, it would be possible to have a short error message with
> a
On 10/12/10 07:36, KIZU Naoko wrote:
> Hi,
> I've got an error message in trying to access Japanese Wikipedia. It
> seems long, but it's not my topic.
> IIRC the message from server was multilingualized years ago and we
> have offered the message with links to other lang
> same messages.
>
> The m
On Fri, Dec 10, 2010 at 1:49 PM, Domas Mituzas wrote:
>> Like you say, though, it's definitely a technical issue to be taken up
>> elsewhere.
>
> Where you will be told that this is 'working as intended'. & is usually
> sent in URLs by broken clients, so we block them as early as possible.
With
Sorry for keeping an off-topic (now) for a while; it won't continue so
long and I'd love to make the below clear before going to buzgilla.
On Fri, Dec 10, 2010 at 9:49 PM, Domas Mituzas wrote:
>> Like you say, though, it's definitely a technical issue to be taken up
>> elsewhere.
>
> Where you wi
> Like you say, though, it's definitely a technical issue to be taken up
> elsewhere.
Where you will be told that this is 'working as intended'. & is usually
sent in URLs by broken clients, so we block them as early as possible.
Domas
___
foundation-l
2010/12/10 KIZU Naoko :
> And thank you for noticing me/us it's somehow weird. Without the
> entity "&" it works - so we might find two things to fix. I'll
> later file the bug on the entity related thing, it seems a pure
> technical thing and need to dig up further here.
The issue there is that y
Hi,
On Fri, Dec 10, 2010 at 9:57 AM, Peter Coombe
wrote:
> On 10 December 2010 00:47, Peter Coombe wrote:
>> On 9 December 2010 23:50, MZMcBride wrote:
>>> KIZU Naoko wrote:
I've got an error message in trying to access Japanese Wikipedia. It
seems long, but it's not my topic.
II
Peter Coombe wrote:
> The 404 error you linked to (http://ja.wikipedia.org/w/&) could
> certainly be improved, though as far as I know it's always been like
> that. Absurd really, how many users who've mistyped an address are
> going to want a database dump?
There's a bug about improving the 404 p
On 10 December 2010 00:47, Peter Coombe wrote:
> On 9 December 2010 23:50, MZMcBride wrote:
>> KIZU Naoko wrote:
>>> I've got an error message in trying to access Japanese Wikipedia. It
>>> seems long, but it's not my topic.
>>> IIRC the message from server was multilingualized years ago and we
>
On 9 December 2010 23:50, MZMcBride wrote:
> KIZU Naoko wrote:
>> I've got an error message in trying to access Japanese Wikipedia. It
>> seems long, but it's not my topic.
>> IIRC the message from server was multilingualized years ago and we
>> have offered the message with links to other lang
>>
KIZU Naoko wrote:
> I've got an error message in trying to access Japanese Wikipedia. It
> seems long, but it's not my topic.
> IIRC the message from server was multilingualized years ago and we
> have offered the message with links to other lang
> same messages.
>
> The message itself seems not c
14 matches
Mail list logo