Forum

1c tries to parse XML on server error 500

Oct 13, 2015 09:51 AM

Interested

Points:: 15
Joined:: Oct 27, 2011

If you try to use some WS which returns 500 (server error) 1c tries to parse returning XML message which does not exist. It is very confusing and makes more difficult to understand the problem.

Request: make error messages more accurate

Code

{DataProcessor.DataProcessor1.Form.Form.Form(11)}: Error calling context method (validarXML)
   Result = WS.validarXML(Base64String(FileData));
because:
Service operation call error:  {http://ats.ws.abaco.com.ec/}:ValidacionXMLImplService:validarXML()
because:
Unknown error. XML parsing error:  - [1,1]
Fatal error: 
Extra content at the end of the document

because:
XML parsing error:  - [1,1]
Fatal error: 
Extra content at the end of the document

Profile

Timofey Bugaevsky	#2 Oct 13, 2015 01:00 PM
Guest Points:: Joined::	Hello, Alexey! Which behavior do you think suits this case?
	Profile

Alexey Gerasimov

Oct 14, 2015 01:01 PM

Interested

Points:: 15
Joined:: Oct 27, 2011

I think the platform should return server error exactly like server does. If it is 404 - then 404, if it is 500 - then 500. Like so:

Code

{DataProcessor.DataProcessor1.Form.Form.Form(11)}: Error calling context method (validarXML)
   Result = WS.validarXML(Base64String(FileData));
because:
Service operation call error:  {http://ats.ws.abaco.com.ec/}:ValidacionXMLImplService:validarXML()
because:
Server returned code: 500 (Internal server error)

Profile

Timofey Bugaevsky	#4 Oct 15, 2015 12:04 AM
Guest Points:: Joined::	Thank you, Alexey. I have submitted this feature request for you.
	Profile