Enable CORS in IIS 8.5 applicationTroubleshooting Windows Authentication problems (no challenge) in IIS 7.5?Which credentials are used when browsing a directory through IISWhy do we get a sudden spike in response times?IIS 8.5: Enable server for anonymous PUT http verbIIS 8.5 Manager: Application Pools and Sites nodes missingIIS ARR/Reverse Proxy 502 Errors for Larger FilesIIS 8.5 cold startHow to remotely recycle an application pool of IIS 8.5?URL Rewrite in IIS 8.5 HTTPS to HTTPS end in gateway eroorAccess Remote Shared Path from IIS 8.5

Multi tool use
Multi tool use

How strong are Wi-Fi signals?

When and what was the first 3D acceleration device ever released?

If a person had control of every single cell of their body, would they be able to transform into another creature?

Would Brexit have gone ahead by now if Gina Miller had not forced the Government to involve Parliament?

the meaning of 'carry' in a novel

Simple fuzz pedal using breadboard

How to know if a folder is a symbolic link?

I unknowingly submitted plagarised work

Were pens caps holes designed to prevent death by suffocation if swallowed?

Which is the common name of Mind Flayers?

Is CD audio quality good enough?

Line of lights moving in a straight line , with a few following

How to pull out the underlying query syntax being used by dataset?

Does the unit of measure matter when you are solving for the diameter of a circumference?

Ticket to ride, 1910: What are the big cities

Is the Indo-European language family made up?

Why is this Simple Puzzle impossible to solve?

What was the idiom for something that we take without a doubt?

Compactness of finite sets

In general, would I need to season a meat when making a sauce?

Flying domestically in the US, is my State Issued ID all I need to get past security?

What is memelemum?

Why doesn't the Earth accelerate towards the Moon?

Would jet fuel for an F-16 or F-35 be producible during WW2?



Enable CORS in IIS 8.5 application


Troubleshooting Windows Authentication problems (no challenge) in IIS 7.5?Which credentials are used when browsing a directory through IISWhy do we get a sudden spike in response times?IIS 8.5: Enable server for anonymous PUT http verbIIS 8.5 Manager: Application Pools and Sites nodes missingIIS ARR/Reverse Proxy 502 Errors for Larger FilesIIS 8.5 cold startHow to remotely recycle an application pool of IIS 8.5?URL Rewrite in IIS 8.5 HTTPS to HTTPS end in gateway eroorAccess Remote Shared Path from IIS 8.5






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















We have a ERP application (Epicor) which provides a REST interface sitting inside of an II 8.5 (win server 2012R2).



No problem doing POST/GET etc using Insomina (a desktop program similar to PostMan)



In IIS we have enabled only Anonymous Authentication.



However, the below request is getting a 401 Error and is blocking because of CORS (even though it has 'Access-Control-Allow-Origin':'*', )



We are using Chrome V74



 const fetcher = (async () => 
const url = 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum'
const raw = fetch(url,
method: 'POST',
mode: 'cors',
headers:
'Accept': 'application/json',
'Authorization': 'Basic xxxxxxx=',
'Access-Control-Allow-Origin':'*',
'Content-Type': 'application/json'
,
body: JSON.stringify()
)
console.log(raw)
const nJob = await raw.json()
console.log(nJob)
return nJob
)


Here is the error:



VM1115:1 OPTIONS https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum 401 (Forbidden)

dispatchInteractiveEvent @ Main.7485fc72.js:8458
Main.html:1 Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://localhost' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.


What settings should we be using on IIS to allow the CORS request to go through?




UPDATE



We got I.T. to add the cors module, and I updated the the section of the web.config but I am still getting an CORS error. Can you tell me what is wrong here?



<httpProtocol>
<customHeaders>
<add name="Access-Control-Allow-Origin" value="*" />
</customHeaders>
</httpProtocol>
<cors enabled="true" failUnlistedOrigins="false">
</cors>




This is the error:



`Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://ysg4206.draper.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.`









share|improve this question
























  • iis.net/downloads/microsoft/iis-cors-module

    – Lex Li
    May 14 at 2:15











  • @LexLi see update.

    – Dr.YSG
    May 15 at 19:33











  • If you dig further into its configuration you should see docs.microsoft.com/en-us/iis/extensions/cors-module/…

    – Lex Li
    May 15 at 20:07

















0















We have a ERP application (Epicor) which provides a REST interface sitting inside of an II 8.5 (win server 2012R2).



No problem doing POST/GET etc using Insomina (a desktop program similar to PostMan)



In IIS we have enabled only Anonymous Authentication.



However, the below request is getting a 401 Error and is blocking because of CORS (even though it has 'Access-Control-Allow-Origin':'*', )



We are using Chrome V74



 const fetcher = (async () => 
const url = 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum'
const raw = fetch(url,
method: 'POST',
mode: 'cors',
headers:
'Accept': 'application/json',
'Authorization': 'Basic xxxxxxx=',
'Access-Control-Allow-Origin':'*',
'Content-Type': 'application/json'
,
body: JSON.stringify()
)
console.log(raw)
const nJob = await raw.json()
console.log(nJob)
return nJob
)


Here is the error:



VM1115:1 OPTIONS https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum 401 (Forbidden)

dispatchInteractiveEvent @ Main.7485fc72.js:8458
Main.html:1 Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://localhost' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.


What settings should we be using on IIS to allow the CORS request to go through?




UPDATE



We got I.T. to add the cors module, and I updated the the section of the web.config but I am still getting an CORS error. Can you tell me what is wrong here?



<httpProtocol>
<customHeaders>
<add name="Access-Control-Allow-Origin" value="*" />
</customHeaders>
</httpProtocol>
<cors enabled="true" failUnlistedOrigins="false">
</cors>




This is the error:



`Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://ysg4206.draper.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.`









share|improve this question
























  • iis.net/downloads/microsoft/iis-cors-module

    – Lex Li
    May 14 at 2:15











  • @LexLi see update.

    – Dr.YSG
    May 15 at 19:33











  • If you dig further into its configuration you should see docs.microsoft.com/en-us/iis/extensions/cors-module/…

    – Lex Li
    May 15 at 20:07













0












0








0








We have a ERP application (Epicor) which provides a REST interface sitting inside of an II 8.5 (win server 2012R2).



No problem doing POST/GET etc using Insomina (a desktop program similar to PostMan)



In IIS we have enabled only Anonymous Authentication.



However, the below request is getting a 401 Error and is blocking because of CORS (even though it has 'Access-Control-Allow-Origin':'*', )



We are using Chrome V74



 const fetcher = (async () => 
const url = 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum'
const raw = fetch(url,
method: 'POST',
mode: 'cors',
headers:
'Accept': 'application/json',
'Authorization': 'Basic xxxxxxx=',
'Access-Control-Allow-Origin':'*',
'Content-Type': 'application/json'
,
body: JSON.stringify()
)
console.log(raw)
const nJob = await raw.json()
console.log(nJob)
return nJob
)


Here is the error:



VM1115:1 OPTIONS https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum 401 (Forbidden)

dispatchInteractiveEvent @ Main.7485fc72.js:8458
Main.html:1 Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://localhost' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.


What settings should we be using on IIS to allow the CORS request to go through?




UPDATE



We got I.T. to add the cors module, and I updated the the section of the web.config but I am still getting an CORS error. Can you tell me what is wrong here?



<httpProtocol>
<customHeaders>
<add name="Access-Control-Allow-Origin" value="*" />
</customHeaders>
</httpProtocol>
<cors enabled="true" failUnlistedOrigins="false">
</cors>




This is the error:



`Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://ysg4206.draper.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.`









share|improve this question
















We have a ERP application (Epicor) which provides a REST interface sitting inside of an II 8.5 (win server 2012R2).



No problem doing POST/GET etc using Insomina (a desktop program similar to PostMan)



In IIS we have enabled only Anonymous Authentication.



However, the below request is getting a 401 Error and is blocking because of CORS (even though it has 'Access-Control-Allow-Origin':'*', )



We are using Chrome V74



 const fetcher = (async () => 
const url = 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum'
const raw = fetch(url,
method: 'POST',
mode: 'cors',
headers:
'Accept': 'application/json',
'Authorization': 'Basic xxxxxxx=',
'Access-Control-Allow-Origin':'*',
'Content-Type': 'application/json'
,
body: JSON.stringify()
)
console.log(raw)
const nJob = await raw.json()
console.log(nJob)
return nJob
)


Here is the error:



VM1115:1 OPTIONS https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum 401 (Forbidden)

dispatchInteractiveEvent @ Main.7485fc72.js:8458
Main.html:1 Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://localhost' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.


What settings should we be using on IIS to allow the CORS request to go through?




UPDATE



We got I.T. to add the cors module, and I updated the the section of the web.config but I am still getting an CORS error. Can you tell me what is wrong here?



<httpProtocol>
<customHeaders>
<add name="Access-Control-Allow-Origin" value="*" />
</customHeaders>
</httpProtocol>
<cors enabled="true" failUnlistedOrigins="false">
</cors>




This is the error:



`Access to fetch at 'https://epicorapp2.draper.com/ERP10.1Test/api/v1/Erp.BO.JobEntrySvc/GetNextJobNum' from origin 'http://ysg4206.draper.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.`






iis






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 15 at 19:34







Dr.YSG

















asked May 13 at 18:44









Dr.YSGDr.YSG

514




514












  • iis.net/downloads/microsoft/iis-cors-module

    – Lex Li
    May 14 at 2:15











  • @LexLi see update.

    – Dr.YSG
    May 15 at 19:33











  • If you dig further into its configuration you should see docs.microsoft.com/en-us/iis/extensions/cors-module/…

    – Lex Li
    May 15 at 20:07

















  • iis.net/downloads/microsoft/iis-cors-module

    – Lex Li
    May 14 at 2:15











  • @LexLi see update.

    – Dr.YSG
    May 15 at 19:33











  • If you dig further into its configuration you should see docs.microsoft.com/en-us/iis/extensions/cors-module/…

    – Lex Li
    May 15 at 20:07
















iis.net/downloads/microsoft/iis-cors-module

– Lex Li
May 14 at 2:15





iis.net/downloads/microsoft/iis-cors-module

– Lex Li
May 14 at 2:15













@LexLi see update.

– Dr.YSG
May 15 at 19:33





@LexLi see update.

– Dr.YSG
May 15 at 19:33













If you dig further into its configuration you should see docs.microsoft.com/en-us/iis/extensions/cors-module/…

– Lex Li
May 15 at 20:07





If you dig further into its configuration you should see docs.microsoft.com/en-us/iis/extensions/cors-module/…

– Lex Li
May 15 at 20:07










1 Answer
1






active

oldest

votes


















0














So you have a couple of problems



The first is that your request is not returning a HTTP 200 OK status (the system your calling). this is a problem with the fetch API it does not support any none 200 status code responses. (fix is to switch to using XMLHttpRequest commonly known as AJAX), you can test this using an application such as Advanced Rest Client and making the request from in there to see what status code it is giving back.



The second you need to tell it GET & OPTIONS requests are allowed with access-control-allow-methods:GET,OPTIONS header. (OPTIONS is what the CORS check uses to do its checks)



The third problem is that your no longer allowed to use the * as a valid Origin you have to supply the origin of the calling system, in this case, the site running the javascript. so this would require your 'IT Department' to engineer the code to use the referer header to know the host and port they need to supply in that header it can be done by a web.config file if they are able to hard code the hostname and port of the calling site.



<httpProtocol>
<customHeaders>
<add name="Access-Control-Allow-Origin" value="example.com,example.com:8080" />
<add name="Access-Control-Allow-Method" value="GET, OPTIONS" />
</customHeaders>
</httpProtocol>


The example above shows both using a standard port of 80 or HTTPS port of 443, and an example of a custom port of 8080



The fourth problem is that the CORS headers are not sent by Javascript I slightly covered this in the third point but your Javascript should not send the headers and to do so will do nothing. The server or website your connecting to has to send the headers as you enabling of the CORS module shows you.






share|improve this answer

























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f967086%2fenable-cors-in-iis-8-5-application%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    So you have a couple of problems



    The first is that your request is not returning a HTTP 200 OK status (the system your calling). this is a problem with the fetch API it does not support any none 200 status code responses. (fix is to switch to using XMLHttpRequest commonly known as AJAX), you can test this using an application such as Advanced Rest Client and making the request from in there to see what status code it is giving back.



    The second you need to tell it GET & OPTIONS requests are allowed with access-control-allow-methods:GET,OPTIONS header. (OPTIONS is what the CORS check uses to do its checks)



    The third problem is that your no longer allowed to use the * as a valid Origin you have to supply the origin of the calling system, in this case, the site running the javascript. so this would require your 'IT Department' to engineer the code to use the referer header to know the host and port they need to supply in that header it can be done by a web.config file if they are able to hard code the hostname and port of the calling site.



    <httpProtocol>
    <customHeaders>
    <add name="Access-Control-Allow-Origin" value="example.com,example.com:8080" />
    <add name="Access-Control-Allow-Method" value="GET, OPTIONS" />
    </customHeaders>
    </httpProtocol>


    The example above shows both using a standard port of 80 or HTTPS port of 443, and an example of a custom port of 8080



    The fourth problem is that the CORS headers are not sent by Javascript I slightly covered this in the third point but your Javascript should not send the headers and to do so will do nothing. The server or website your connecting to has to send the headers as you enabling of the CORS module shows you.






    share|improve this answer





























      0














      So you have a couple of problems



      The first is that your request is not returning a HTTP 200 OK status (the system your calling). this is a problem with the fetch API it does not support any none 200 status code responses. (fix is to switch to using XMLHttpRequest commonly known as AJAX), you can test this using an application such as Advanced Rest Client and making the request from in there to see what status code it is giving back.



      The second you need to tell it GET & OPTIONS requests are allowed with access-control-allow-methods:GET,OPTIONS header. (OPTIONS is what the CORS check uses to do its checks)



      The third problem is that your no longer allowed to use the * as a valid Origin you have to supply the origin of the calling system, in this case, the site running the javascript. so this would require your 'IT Department' to engineer the code to use the referer header to know the host and port they need to supply in that header it can be done by a web.config file if they are able to hard code the hostname and port of the calling site.



      <httpProtocol>
      <customHeaders>
      <add name="Access-Control-Allow-Origin" value="example.com,example.com:8080" />
      <add name="Access-Control-Allow-Method" value="GET, OPTIONS" />
      </customHeaders>
      </httpProtocol>


      The example above shows both using a standard port of 80 or HTTPS port of 443, and an example of a custom port of 8080



      The fourth problem is that the CORS headers are not sent by Javascript I slightly covered this in the third point but your Javascript should not send the headers and to do so will do nothing. The server or website your connecting to has to send the headers as you enabling of the CORS module shows you.






      share|improve this answer



























        0












        0








        0







        So you have a couple of problems



        The first is that your request is not returning a HTTP 200 OK status (the system your calling). this is a problem with the fetch API it does not support any none 200 status code responses. (fix is to switch to using XMLHttpRequest commonly known as AJAX), you can test this using an application such as Advanced Rest Client and making the request from in there to see what status code it is giving back.



        The second you need to tell it GET & OPTIONS requests are allowed with access-control-allow-methods:GET,OPTIONS header. (OPTIONS is what the CORS check uses to do its checks)



        The third problem is that your no longer allowed to use the * as a valid Origin you have to supply the origin of the calling system, in this case, the site running the javascript. so this would require your 'IT Department' to engineer the code to use the referer header to know the host and port they need to supply in that header it can be done by a web.config file if they are able to hard code the hostname and port of the calling site.



        <httpProtocol>
        <customHeaders>
        <add name="Access-Control-Allow-Origin" value="example.com,example.com:8080" />
        <add name="Access-Control-Allow-Method" value="GET, OPTIONS" />
        </customHeaders>
        </httpProtocol>


        The example above shows both using a standard port of 80 or HTTPS port of 443, and an example of a custom port of 8080



        The fourth problem is that the CORS headers are not sent by Javascript I slightly covered this in the third point but your Javascript should not send the headers and to do so will do nothing. The server or website your connecting to has to send the headers as you enabling of the CORS module shows you.






        share|improve this answer















        So you have a couple of problems



        The first is that your request is not returning a HTTP 200 OK status (the system your calling). this is a problem with the fetch API it does not support any none 200 status code responses. (fix is to switch to using XMLHttpRequest commonly known as AJAX), you can test this using an application such as Advanced Rest Client and making the request from in there to see what status code it is giving back.



        The second you need to tell it GET & OPTIONS requests are allowed with access-control-allow-methods:GET,OPTIONS header. (OPTIONS is what the CORS check uses to do its checks)



        The third problem is that your no longer allowed to use the * as a valid Origin you have to supply the origin of the calling system, in this case, the site running the javascript. so this would require your 'IT Department' to engineer the code to use the referer header to know the host and port they need to supply in that header it can be done by a web.config file if they are able to hard code the hostname and port of the calling site.



        <httpProtocol>
        <customHeaders>
        <add name="Access-Control-Allow-Origin" value="example.com,example.com:8080" />
        <add name="Access-Control-Allow-Method" value="GET, OPTIONS" />
        </customHeaders>
        </httpProtocol>


        The example above shows both using a standard port of 80 or HTTPS port of 443, and an example of a custom port of 8080



        The fourth problem is that the CORS headers are not sent by Javascript I slightly covered this in the third point but your Javascript should not send the headers and to do so will do nothing. The server or website your connecting to has to send the headers as you enabling of the CORS module shows you.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 22 at 0:05

























        answered May 21 at 23:54









        Martin BarkerMartin Barker

        226115




        226115



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f967086%2fenable-cors-in-iis-8-5-application%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Lr16jvZbQIaK3wzM1X R79J9B4PDXCAzD7EsA5
            lgp xpvzzucWZ,sL3ImCo1r235 xST

            Popular posts from this blog

            RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

            Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

            Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020