Khaladaadka 407 ee proxy ee ka yimaadda DTD iyo kheyraadka XML ee dibadda

Raadso 407 aan la filayn inta lagu jiro beddelka dukumeentiga oo loo gudbinayo DTD, schema ama kheyraad kale oo dibadda ah oo uu parser-ku furo.

Dukumeenti maxalli ah weli wuxuu sababi karaa 407 inta lagu jiro beddelka. XML-kiisu wuxuu sheegi karaa DTD, schema ama entity, waxaana renderer-ku soo qaadan karaa styles ama sawirro. Macmiilka guuldarraysta wuxuu ku jiri karaa parser-kaas gudihiisa, ka dib markii soo dejinta asalka ah dhammaatay.

Hayso exception stack iyo URI-da la codsaday, ka dibna la jaanqaad sheegida input-ka ama tixraacyada kheyraadka. Codsi DTD oo loo diro host caadi ah waa hawl ka duwan codsiga bogga. Beddelka HTML-ilaa-PDF sidoo kale wuu guuldarrayn karaa marka kheyraad fog la soo qaadanayo.

Gelinta .NET XmlReader oo qandaraaskeedu mamnuucayo DTD iyo xallinta dibadda, isticmaal:

var settings = new XmlReaderSettings
{
    DtdProcessing = DtdProcessing.Prohibit,
    XmlResolver = null
};

U gudbi dejintaas qaybta dhab ahaan parser-ka u sameysa dukumeentiga. DtdProcessing wuxuu doortaa sida DTD loo maareeyo; XmlResolver wuxuu xakameeyaa gelitaanka dibadda. Prohibit wuu diidayaa dukumeenti leh DTD—ma tirtiro sheegida. Haddii hawsha loo baahan yahay mid, dooro xal maxalli ah oo la ansixiyay ama resolver si cad loo jiheeyay.

Hayso qiimaha caadiga ah oo ku xiran API/runtime. XmlReaderSettings waxay caadi ahaan isticmaashaa Prohibit, resolver-keeduna wuxuu isu beddelay null laga bilaabo .NET Framework 4.5.2. Beddelaha saddexaad wuu ka gudbi karaa ama parser kale ayuu isticmaali karaa.

Beddelka sheegida XHTML oo loo beddelo HTML doctype waxay saameyn kartaa hal beddele, laakiin ma habaynto proxy-ga. Go'aami kheyraadka loo baahan yahay iyo siyaasadda soo dejintooda; aqoonsiga macmiilka bogga horreeya ma aqoonsado macmiilkan labaad.

Maqaallo la xiriira