Contributions
Re: 403 Error When Running Test In Test Suite
I found out what the issue was. On our new Win2012 servers we had some setting setup to help stop DOS attacks. This cuased the test to fails after so many were runs successfully because the server saw the request as DOS attack because of the number of request coming from the same IP in such a quick manner. We disabled this feature and that took care of the issue.7.4KViews0likes0CommentsRe: 403 Error When Running Test In Test Suite
I already did the test individual. I can go straight down the list and run each test individual and they all pass, it is only when run together as a "test suite" that at some point all the test start failing. But runnign them manually and they pass.7.4KViews0likes1CommentRe: 403 Error When Running Test In Test Suite
No, as stated in 2 previous emails all the steps run fine when I run the rest by itself but all the test fail after a certian number of test run. So if I move the first test that fails up one place then it passes and the one it switched places with now fails. All the test in this one Test Suite hit the same URL.7.4KViews0likes3CommentsRe: 403 Error When Running Test In Test Suite
No, it does not happen all the time only when I run all the test under a test siite. If I run the test indivudually then the test pass without any issues. And the error does not make sense becuase it is access denied, but if that was they case why to the same test rrun when I run the test individually. See attachments7.5KViews0likes0Comments403 Error When Running Test In Test Suite
When I run a test it passes, but when I run all the test through the test suite Iget a 403 (Access Forbidden). So why do the same test run when run directly but fail when run through the test suite. And to make things even more confusing there are other test tha do run in the test Suite hititng the same URL, just different ".asmx) page.Solved7.5KViews0likes8CommentsRe: Invalid charater entity reference: � - Help Needed
No it is not validatinb against a scheme. But the bigger question is why are these characters being shown in the return message in SoapUI and Firefox, but not IE. I have checked the code and the fields are null in the database and I am not sending these characters back in those fields either. So I am not sure where they are being added. Is there a way to make SoapUI make the call usign the IE renderign enging instead of what it uses by default? If so, how do I do this?1.1KViews0likes0CommentsInvalid charater entity reference: � - Help Needed
I am getting the following error on a response I am getting back from web service. The field the � is in is a null field in the database. I get a parsing error accessing the web service in Firefox because of the same characters being in the filed, but do not get the parse error when I use IE. So is there anyway I can SoapUI to treat this the same way as IE does and not get the "�" characters in the empty fields? I checked the web services and I am not returning those charcters in the XML so those have to be being added by the browse/SoapUI (rendering engine). If I put a space in the database the error also goes away, but that is unacceptable. I shoudl be able to return a null field back in the XML and have the tag just be empty. Any help will be appreciatd.1.5KViews0likes3Comments