2. Summary
  3. Files
  4. Support
  5. Report Spam
  6. Create account
  7. Log in

Ticket #1336 (closed: wontfix)

Opened 4 years ago

Last modified 11 months ago

HA Proxy: Mantis XML issue

Reported by: rombert Owned by: burley
Keywords: HA_PROXY Cc:
Private: no

Description

https://sourceforge.net/apps/mantisbt/mylyn-mantis/api/soap/mantisconnect.php

Has a HTML header + footer, but should not. This worked before migrating under the 'sourceforget.net/apps/' url.

Change History

Changed 4 years ago by hinojosa

  • keywords SOG added; mantis removed
  • owner set to cmaloney
  • status changed from new to assigned

Changed 4 years ago by burley

  • keywords PEND added

Greetings,

The page has HTML content, that is meant for viewing from a standard browser afaict. Thus, the header and footer add appears to be legitimate to me. The WSDL content that is returned is done so without the header/footer, as would be expected. What problem is this causing?

Thank you,

David Burley
Systems Programmer/Analyst, SourceForge.net

Changed 4 years ago by rombert

David,

The page also acts as an entry point for SOAP calls - whose responses are now wrapped in HTML. A simple 

mc_version

now generates an HTML answer, instead of XML.

The error reported on the client side in my case is

org.xml.sax.SAXException: Bad envelope tag:  html

Thank you,

Robert Munteanu

Changed 4 years ago by hinojosa

  • keywords PEND removed

Changed 4 years ago by burley

  • keywords PEND added

Greetings,

When I connect to the page via telnet, like so:

GET /apps/mantisbt/mylyn-mantis/api/soap/mantisconnect.php HTTP/1.1
HOST: sourceforge.net

I get a HTML response:

HTTP/1.1 200 OK
Date: Tue, 23 Jun 2009 23:41:47 GMT
Server: Apache/2.2.0 (Fedora)
X-Powered-By: PHP/5.2.8
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

15a50

                <html><head><title>NuSOAP: MantisConnect</title>
...

This is accessing the application directly, without our proxy that adds the header/footer content that you want excised. How can I make a request to this page to duplicate your issue manually so I have a reproduceable case?

Thank you,

David Burley

Changed 4 years ago by rombert

I suggest you do the following:

- download/webstart SoapUI from http://www.soapui.org/
- Create a new project specifying the WDSL as https://sourceforge.net/apps/mantisbt/mylyn-mantis/api/soap/mantisconnect.php?wsdl
- Try to invoke one of the generated calls.

At that moment you will get an HTML response instead of XML.

Changed 4 years ago by hinojosa

  • keywords PEND removed

Changed 4 years ago by burley

  • keywords PEND added

Please advise: What's your client's IP address?

Changed 4 years ago by rombert

Requests might be coming in from both

- 81.180.230.218
- 81.181.93.37

Changed 4 years ago by rombert

Is there any way I can help you track down the root cause of this problem?

Changed 4 years ago by jwigglesworth

  • keywords PEND removed

Changed 4 years ago by mstinson

  • keywords HA_MANTIS added
  • owner changed from cmaloney to burley

Changed 4 years ago by nhruby

  • keywords PEND added

Hi,

We are aware of this issue and are working toward a solution. I currently do not know a timeline as to when this issue will be resolved, but it is being actively worked on.

nathan hruby
System Programmer/Analyst II
SourceForge.net

Changed 4 years ago by rombert

Hi,

Are there any updates on this issue?

Thanks,

Robert

Changed 4 years ago by rolfkleef

I'd love to hear an update too. What does "actively worked on" mean, and how can we help?

Thanks,
Rolf.

Changed 4 years ago by hinojosa

  • keywords ENGR HA_PROXY SPT-126 added; SOG HA_MANTIS PEND removed

Hi,

This issue is being investigated by our engineering team. I do not have an ETA as yet. Updates will be posted to the ticket.

The issue is internal and requires a bit of effort on an infrastructure. Actively means that the team has it on their plate, is doing the necessary investigation, and working to get the right solution in place.

If you need anything else, please post a response to this request.

Cheers!,

Daniel Hinojosa - Sr. Manager, SourceForge.net Support

P.S., Be sure to monitor our Site Status page.

Changed 3 years ago by spchamp

Thanks for the update. Glad to hear the sf.net folks are tracking, about it.

Just to add some exposition to the pot: It appears that this issue -- on projects hosted at SourceForge.net and utilizing SourceForge's built-in Mantis BT feature -- is preventing successful utilization of the Mylyn-Mantis plugin for the Eclipse IDE, onto the Mantis BT sites being used in the said SourceForge.net projects. This, in turn, may affect SourceForge hosted projects that are depending on Mantis BT for issue tracking, development roadmap planning, and any other features provided by Mantis BT. Not to be a burden about it, I'm just looking forward to the successful closure of this issue, and once again, glad to hear it's being worked on. Thanks a heap, so to speak.

Changed 3 years ago by ahoehma

Hi,
the QCMylyn Team would be happy if this bugs will be fixed asap.
We can't use the eclipse mantis mylyn connector :-(
Regards
Andreas

Changed 3 years ago by hinojosa

  • summary changed from Mantis SOAP API pages wrapped in html content to HA Proxy: Mantis XML issue

Changed 3 years ago by ekkescorner

would be great to get MantisBT work with Mylyn
ekke

Changed 3 years ago by rolfkleef

bump... 6 months and 4 months ago you were actively working on the issue, any news on where this is now?

Changed 3 years ago by hinojosa

Hi,

The plan with this is to change the infrastructure to resolve this and other related issues. The target for this is April. I'd expect a resolution at the early part of the month of May.

Best regards,

Daniel Hinojosa - Sr. Manager, SourceForge.net Support

P.S., Be sure to monitor our Site Status.

Changed 3 years ago by rombert

Is this bug still on track to be resolved in May?

Thanks,

Robert

Changed 3 years ago by robsonximenes

We from demoiselle project need that solution.

It's very useful for us...

This ticket is very old...

Changed 3 years ago by rolfkleef

hi, the Hosted Apps maintenance was scheduled for April 26, according to https://sourceforge.net/apps/wordpress/sourceforge/2010/04/23/hosted-apps-maintenance-for-today-has-been-postponed-2010-04-23/ but no news after that.

Since we're beyond "the early part of the month of May", is it possible to get an update on the situation and possibly a new target date? Thanks :-)

Changed 3 years ago by rombert

I second that. It's inconvenient that it does not work, but knowing a definite timeline exists would be very helpful.

Thanks,

Robert

Changed 3 years ago by cparker15

Just adding my name to the list of people interested in a resolution. I'm also trying to use Mylyn-Mantis to connect to SourceForge-hosted Mantis.

Changed 3 years ago by ctsai

  • keywords ENGR SPT-126 removed

Changed 3 years ago by professorf

Just to show the difference.

sf.net:

POST /userapps/mantisbt/professorf/api/soap/mantisconnect.php HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.mantisbt.org/bugs/api/soap/mantisconnect.php/mc_version"
User-Agent: Axis/1.4
Host: sourceforge.net
Content-Length: 392
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:mc_version soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://futureware.biz/mantisconnect"/></soapenv:Body></soapenv:Envelope>

HTTP/1.1 200 OK
X-SFX-Webhead: sfs-web-6
Set-Cookie: sfha_mantisbt_BIGipServerPOOL_sfnet_sfa-web_51264=891362732.16584.0000
Date: Mon, 13 Sep 2010 15:26:06 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.9
Connection: close
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
fff8
..<html><head><title>NuSOAP: MantisConnect</title>

And the correct one:

POST /mantisbt-1.2.2/api/soap/mantisconnect.php HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.mantisbt.org/bugs/api/soap/mantisconnect.php/mc_version"
User-Agent: Axis/1.4
Content-Length: 392
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:mc_version soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://futureware.biz/mantisconnect"/></soapenv:Body></soapenv:Envelope>

HTTP/1.1 200 OK
Date: Mon, 13 Sep 2010 15:26:42 GMT
Server: Apache/2.2.16 (Unix)
X-Powered-By: PHP/5.3.3
Cache-Control: private, max-age=10800, pre-check=10800
X-SOAP-Server: NuSOAP/0.9.5 (1.123)
Set-Cookie: PHPSESSID=0b26d72f3c2393e698d1279fc5e420e3; path=/; HttpOnly
Last-Modified: Wed, 04 Aug 2010 18:57:56 GMT
Content-Length: 533
X-Powered-By: Mono
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><ns1:mc_versionResponse xmlns:ns1="http://futureware.biz/mantisconnect"><return xsi:type="xsd:string">1.2.2</return></ns1:mc_versionResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

Changed 3 years ago by tjaehnel

Is there any news about when this issue will be fixed?
Or some workaround?

I'm in urgent need of using the hosted mantis with Mylyn.

Tobias

Changed 3 years ago by m31

Hi,

we also want to connect to the sourceforge Mantis via Mylyn.
Are there any news about this issue? Should we change to another Mantis server?
You still work on it, do you?

m31

Changed 2 years ago by rombert

Ding-dong! Any news for this Christmas?

Changed 2 years ago by rombert

There are currently five open tickets related to the MantisBT SOAP access. Can we at least merge them? It makes it easier to track for various people who want to see this fixed.

https://sourceforge.net/apps/trac/sourceforge/ticket/1336
https://sourceforge.net/apps/trac/sourceforge/ticket/2203
https://sourceforge.net/apps/trac/sourceforge/ticket/2720
https://sourceforge.net/apps/trac/sourceforge/ticket/3624
https://sourceforge.net/apps/trac/sourceforge/ticket/5789

Changed 2 years ago by lbettini

any news?

Changed 2 years ago by cobexer

either fix this, or state that you won't fix it. seriously 21 Months open and no fix.

Changed 2 years ago by christoph_pickl

VOTE UP!

Changed 2 years ago by robsonximenes

It's a shame ... SF does not respect us.

Just say if they will do something ...

Changed 2 years ago by mike_mvpi

Vote Up! Does it really take 22 month to fix this?

Changed 2 years ago by g_balage

Is there any chance for the SF.net team to resolve this? You can't or don't want to fix this problem?

Changed 2 years ago by lbettini

I vote as well (though I don't see any means to vote like in bugzilla)

Changed 2 years ago by viras

Any update on this issue? I would really appreciate a working SOAP API for mantis!

Changed 2 years ago by nricheton

+1

Changed 22 months ago by jjgl7

+1

Please fix it.

Thanks.

Changed 22 months ago by may-bee

For our project we also decided to use this great management tool mantis. Hopefully this issue will be fixed soon. I think it is really necessary for a productive developer environment.

VOTE UP!

Changed 20 months ago by calimero100582

+1

Changed 20 months ago by rombert

Hi,

It seems that the situation has changed a bit with the activation of the XMLRPC Plugin for Trac ( https://sourceforge.net/p/forge/documentation/Trac%20XMLRPC/ ).

Now the response is SOAP but with some strange 'META' tags interleaved:

<META NAME="sfhaproxy" CONTENT="NOFOOTER,NOHEADER">
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
        <META NAME="sfhaproxy" CONTENT="NOFOOTER,NOHEADER">
        <SOAP-ENV:Body>
                <ns1:mc_versionResponse xmlns:ns1="http://futureware.biz/mantisconnect">
                        <return xsi:type="xsd:string">1.1.8</return>
                </ns1:mc_versionResponse>
        </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Those two META tags are all that is breaking SOAP output. Please look into this, the solution seems to be frustratingly close.

Thanks again for your efforts!

Changed 20 months ago by rombert

Besides the above issue - inserted META tags - which can be worked around with enough determination , the user is never authenticated. I tried setting HTTP authentication, MantisBT username/password authentication and both.

When using http I get 'access denied' from Mantis . When using https I get redirected to http://sourceforge.net/apps/mantisbt/mylyn-mantis/ .

I would think that if you managed to allow XML-RPC calls for Trac, the mechanism is there to allow SOAP calls for MantisBT as well, so please look into this.

Changed 13 months ago by rhenri

Any update on this issue?

Changed 11 months ago by ctsai

  • status changed from assigned to closed
  • resolution set to wontfix

Greetings,

We've announced today that we will be retiring the Hosted Apps platform. There are many reasons for this, but in the end, it comes down to the fact that we haven't had, nor will we have the resources to maintain this platform (as evidenced by how long this bug, among with many others, have been unaddressed). As we are retiring this service, I'm going to have to close this as "wontfix".

As stated in the blog post, we are writing documentation on how to migrate your data off the platform, and we want to make sure you have proper data dumps. If any of you are having issues with the backup utility, or with the migration instructions (once they're available), please log a new ticket on that. We want to help.

Regards,
Chris Tsai, SourceForge.net Support

Note: See TracTickets for help on using tickets.

© 2013 SourceForge. All Rights Reserved. SourceForge is a Dice Holdings, Inc. company   Terms of Use - Privacy Policy - Cookies/Opt Out