Re: [xliff] Link to registry.txt is now forbidden

[Chet Ensign <chet.ensign@oasis-open.org>]

Hello Yves, 

I got a reply back from our IT support folks: 

"Hey Chet,

We recently restricted access to this feature b/c it was causing performance problems and taking the site offline. However, if Yves updates the below URL to the following, note the extra query parameter isdir=0, it will work. This is the correct URL and won’t get blocked.

https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff2-fragid/registry.txt?op=dl&isdir=0 "

Please try that out and let me know if it works. 

Best, 

/chet

On Wed, Aug 30, 2017 at 12:43 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

Hi Chet,

 

Yes, we can access the page, but the op=dl parameter does not work anymore.

The problem is that we can’t use the HTML-wrapped representation provided of the link without the parameter. The parameter gives the real file.

 

Thanks for looking into it.

 

Cheers,

-yves

 

Yves Savourel
Localization Solutions Architect | t: 303.951.4523 | f: 303.516.1701 | ENLASO®

 

From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Sent: Wednesday, August 30, 2017 10:34 AM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF Main List <xliff@lists.oasis-open.org>
Subject: Re: [xliff] Link to registry.txt is now forbidden

 

Hi Yves, 

 

I just spotted this. I can navigate the tree to https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff2-fragid/registry.txt?sc=1 successfully but I also get denied access when I follow your link. Is it possible that problem is with the op=dl or did this always work in the past? 

 

I know next to nothing about svn by the way, just noting what I see. 

 

Meanwhile I will check with our IT support guys... 

 

/chet

 

 

On Wed, Aug 30, 2017 at 12:19 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

Hi,

 

The link https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff2-fragid/registry.txt?op=dl that allows us to download the registry file for XLIFF 2.x extensions has now its access restricted by OASIS. We get a Forbidden 403 error now when trying to access it.

 

This link is used by unit tests in continuous builds for XLIFF 2 libraries, so those builds now fail. It’s also used by deployed applications.

 

Bryan/David: Could you see with OASIS if the rights for that file be reset to what they were before?

 

Thanks,

-yves

 

 

Yves Savourel
Localization Solutions Architect | ENLASO®
4888 Pearl East Circle | Suite 300E | Boulder | Colorado 80301
t: 303.945.3759 | f: 303.516.1701
An ISO 9001:2015 certified company

 

Confidentiality Notice
The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.

 

 

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393