Forum Discussion
Syntax for local files in Edge Enterprise IE mode for sitelist.xml
brw02005 Hello! My understanding is that when creating the sitelist.xml file, the URL should not contain protocols. Here is a screenshot from Schema v.2 Guidance
It might be that the "file://" portion is causing issues with the parsing.
If you need additional assistance, you can reach out to Support for Business or App Assure: Support - Microsoft Edge Developer. Thanks!
-Kelly
Does not work just writing the local path either. If there is no known syntax reference for local files going to assume that this will never work which is strange as it works from the manually add field where it forgets it in 30 days so strange sitelist.xml does not support that. I have read the same documentation you are presenting.
- Simon_JaklitschDec 04, 2023Copper Contributor
brw02005 Hi same parsing error in my place. Checked everything but edge ignores the first ":" so the configured URL in sitelist.xml is not the same in adresslist of the edge browser
site url="file:///c:/somepath/file" in sitelist.xml then
browser: file:///c:/somepath/file vs. edge://compat listing: *://file//c:/somepath/file and if i remove the file:/// (site url="c:/somepath/file") it shows in the edge://compat *://c/somepath/filei hope we get a fix for that
Local filepaths worked for us till Sept /Aug 23
OS: Win10: 22H2, 21H2 - Win11: 23H2 no difference
- Kelly_YDec 04, 2023
Microsoft
Simon_Jaklitsch Hello - Can you confirm that this used to work previously? And during around Aug/Sept 2023, something changed, and it is now not working? Do you know if you updated to a new version of Microsoft Edge around the time that it stopped working? What version of Edge are you currently using? Thanks!
-Kelly
- Simon_JaklitschDec 05, 2023Copper Contributor
Kelly_Y HI our employees have to do a report every month and they told me that in july they could view the xml report without a problem and after vacation in aug / sep the report did not show up (blanc white page in edge because the parsing didnt work correct). We made no changes to the sitelist.xml so in my opinion the problem is located in the edge browser.
currently we use Version 119.0.2151.72 (Offizielles Build) (64-Bit)
we have auto update in place so if there is an update from edge we get it.
wbr Simon