社区
XML/XSL
帖子详情
the XML response that was returned from the server is invalid
laosan
2007-04-06 06:25:03
PHP中出现的。
首先声明不是编码的问题,全部是英文,全部是utf8,没有涉及到中文。
...全文
415
4
打赏
收藏
the XML response that was returned from the server is invalid
PHP中出现的。 首先声明不是编码的问题,全部是英文,全部是utf8,没有涉及到中文。
复制链接
扫一扫
分享
转发到动态
举报
AI
作业
写回复
配置赞助广告
用AI写文章
4 条
回复
切换为时间正序
请发表友善的回复…
发表回复
打赏红包
cloudgamer
2007-04-14
打赏
举报
回复
不支持白键
cds27
2007-04-09
打赏
举报
回复
我支持qqhe325() 的看法
laosan
2007-04-09
打赏
举报
回复
这个是IE的alert信息,后面是一串xml源文件字符,最后好像还有一行:
you have whitespace in your response.
qqhe325
2007-04-08
打赏
举报
回复
是从SERVER返回的XML有问题吧,在SERVER保存看下~~?
UPnP_Programming_Guide
Linux SDK for UPnP Devices v1.4 Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3 About Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4 The API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1 Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1.1 UPNP E SUCCESS [0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.2 UPNP E
INVALID
HANDLE [-100] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.3 UPNP E
INVALID
PARAM [-101] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.4 UPNP E OUTOF HANDLE [-102] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.5 UPNP E OUTOF MEMORY [-104] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.6 UPNP E INIT [-105] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.7 UPNP E
INVALID
DESC [-107] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.8 UPNP E
INVALID
URL [-108] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.9 UPNP E
INVALID
SERVICE [-111] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.10 UPNP E BAD
RESPONSE
[-113] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.11 UPNP E
INVALID
ACTION [-115] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.12 UPNP E FINISH [-116] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.13 UPNP E INIT FAIL
ED
[-117] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.14 UPNP E BAD HTTPMSG [-119] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.15 UPNP E ALREADY REGISTER
ED
[-120] . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.16 UPNP E NETWORK ERROR [-200] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.17 UPNP E SOCKET WRITE [-201] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.18 UPNP E SOCKET READ [-202] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1.19 UPNP E SOCKET BIND [-203] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1.20 UPNP E SOCKET CONNECT [-204] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1.21 UPNP E OUTOF SOCKET [-205] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1.22 UPNP E LISTEN [-206] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1.23 UPNP E TIM
ED
OUT [-207] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1.24 UPNP E SOCKET ERROR [-208] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1.25 UPNP E CANCEL
ED
[-210] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1.26 UPNP E SUBSCRIBE UNACCEPT
ED
[-301] . . . . . . . . . . . . . . . . . . . . . . 14 4.1.27 UPNP E UNSUBSCRIBE UNACCAPT
ED
[-302] . . . . . . . . . . . . . . . . . . 14 4.1.28 UPNP E NOTIFY UNACCEPT
ED
[-303] . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1.29 UPNP E
INVALID
ARGUMENT [-501] . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.30 UPNP E FILE NOT FOUND [-502] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.31 UPNP E FILE READ ERROR [-503] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.32 UPNP E EXT NOT
XML
[-504] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.33 UPNP E NOT FOUND [-507] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1.34 UPNP E INTERNAL ERROR [-911] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.2 Constants, Structures, and Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.2.3 UPnP EventType — The reason code for an event callback. . . . . . . . 17 4.2.5 Upnp SType — Represents the di?erent types of searches that can be perform
ed
using the SDK for UPnP Devices API. . . . . . . . . . . . . . . . . . . 22 4.2.6 Upnp DescType — Specifies the type of description in UpnpRegis- terRootDevice2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.2.7 Upnp Action Request —
Return
ed
as part of a UPNP CONTROL ACTION COMPLETE callback. . . . . . . . . . . 25 4.2.8 Upnp State Var Request — Represents the request for current value of a state variable in a service state table. . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.2.9 Upnp State Var Complete — Represents the reply for the current value of a state variable in an asynchronous call. . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2.10 Upnp Event —
Return
ed
along with a UPNP EVENT RECEIV
ED
callback. . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.2.11 Upnp Discovery —
Return
ed
in a UPNP DISCOVERY RESULT callback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.2.12 Upnp Event Subscribe —
Return
ed
along with a UPNP EVENT SUBSCRIBE COMPLETE or UPNP EVENT UNSUBSCRIBE COMPLETE callback. . . . . . 35 4.2.13 Upnp Subscription Request —
Return
ed
along with a UPNP EVENT SUBSCRIPTION REQUEST callback. . . . . . . 37 4.2.14 UpnpVirtualDirCallbacks — The UpnpVirtualDirCallbacks struc- ture contains the pointers to file-relat
ed
callback functions a device ap- plication can register to virtualize URLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 4.3 Initialization and Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.4 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.5 Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 4.6 Eventing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 4.7 Control Point HTTP API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 4.8 Web
Server
API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5 Optional Tool APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Delphi7.1 Update
Delphi 7.1 Update Release Notes=======================================================This file contains important supplemental and late-breakinginformation that may not appear in the main productdocumentation, and supers
ed
es information contain
ed
in otherdocuments, including previously install
ed
release notes.Borland recommends that you read this file in its entirety.NOTE: If you are updating a localiz
ed
version of Delphi 7, visit the Borland Register
ed
User web site to obtain a localiz
ed
readme file that may contain important late- breaking information not includ
ed
in this readme file.IMPORTANT: Delphi must be clos
ed
before installing this update. =====================================================CONTENTS * INSTALLING THIS UPDATE * UPDATING LOCALIZ
ED
VERSIONS OF DELPHI 7 * KNOWN ISSUES * ISSUES ADDRESS
ED
BY THIS UPDATE - IDE - CORE DATABASE - DATASNAP - DBGO (ADO COMPONENTS) - dbExpress - dbExpress COMPONENTS AND DB VCL - dbExpress CORE DRIVER AND METADATA - dbExpress VENDOR ISSUES - dbExpress CERTIFICATION - WEB SNAP - ACTIVEX - COMPILER - RTL - VCL - THIRD PARTY - BOLD FOR DELPHI * VERIFYING THAT THE UPDATE WAS SUCCESSFUL * FILES INSTALL
ED
BY THIS UPDATE =======================================================INSTALLING THIS UPDATE* This update can not be appli
ed
to Delphi 7 Architect Trial version. * This update can not be remov
ed
after it is install
ed
.* You will ne
ed
the original Delphi 7 installation CD available to install this update.* To install this update from the CD, insert the CD, and launch the d7_ent_upd1.exe file appropriate for your locale.* To install this update from the Web, double-click the self-executing installation file and follow the prompts. * The Delphi 7 documentation PDF files are available on the update CD.========================================================UPDATING LOCALIZ
ED
VERSIONS OF DELPHI 7* This update can be appli
ed
only to the English version of Delphi 7. There are separate updates for the German, French and Japanese ver
xajax:Error: the
XML
response
that was
return
ed
from the
server
is
invalid
.
xml
处理指令不在外部实体的开始部分位置...
这几天调试xajax,总是报错Error: the
XML
response
that was
return
ed
from the
server
is
invalid
. 在firefox的错误控制台中,提示:
xml
处理指令不在外部实体的开始部分位置 经过反复的调试,最后发现原来是<?php ?> 后面多了一个空格,导致了ajax的
response
Xml
前面也多了一个空格,...
xAjax 乱码的解决
xAjax在家里的电脑上调试好的代码,拷贝到公司的电脑上使用就提示错误: Error:the
XML
response
that was
return
ed
from the
server
is
invalid
. 原因1及解决:xajax 使用变量前需要首先定义,即给个初值就可以了。 原因2及解决:编码的原因。xajax 中返回的
xml
数据默认是以 ut
Invalid
response
document
return
ed
from
Xml
Rpc
server
Invalid
Server
Response
- The
response
to the blogger.getUsersBlog method receiv
ed
from the weblog
server
was
invalid
: Its probably one of two things. 1) Rogue plugins (you said "practically" no p
XML/XSL
8,907
社区成员
22,678
社区内容
发帖
与我相关
我的任务
XML/XSL
XML/XSL相关问题讨论专区
复制链接
扫一扫
分享
社区描述
XML/XSL相关问题讨论专区
社区管理员
加入社区
获取链接或二维码
近7日
近30日
至今
加载中
查看更多榜单
社区公告
暂无公告
试试用AI创作助手写篇文章吧
+ 用AI写文章