Maven, MitmProxy version 9: AttributeError: module 'mitmproxy.http' has no attribute 'HTTPResponse'

[bp32891]

Hello,

I recently started a Maven project using mitmproxy-java. Anytime I try to change the status code of an intercepted call, I get this error: AttributeError: module 'mitmproxy.http' has no attribute 'HTTPResponse'

`List messages = new ArrayList<>();

    MitmproxyJava proxy = new MitmproxyJava("/Library/Frameworks/Python.framework/Versions/3.10/bin/mitmdump", (InterceptedMessage m) -> {
        messages.add(m);
        m.getResponse().setBody("Hi from Test".getBytes(StandardCharsets.UTF_8));
        m.getResponse().getHeaders().add(new String[]{"myTestResponseHeader", "myTestResponseHeaderValue"});
        m.getResponse().setStatusCode(500);
        return m;
    });
    proxy.start();

    Unirest.setProxy(new HttpHost("localhost", 8080));
    HttpResponse<String> response = Unirest.get("http://appium.io").asString();

    driver.get("http://appium.io");

    System.out.println("RESPONSE");
    System.out.println(messages.get(0));

    TimeUnit.SECONDS.sleep(15);

    proxy.stop();

    assertThat(response.getBody()).isEqualTo("Hi from Test");

    final InterceptedMessage firstMessage = messages.get(0);

    assertThat(firstMessage.getRequest().getUrl()).startsWith("http://appium.io/");
    assertThat(firstMessage.getRequest().getHeaders()).containsOnlyOnce(new String[]{"myTestHeader", "myTestValue"});
    assertThat(firstMessage.getResponse().getHeaders()).containsOnlyOnce(new String[]{"myTestResponseHeader", "myTestResponseHeaderValue"});
    System.out.println(firstMessage.getResponse().getStatusCode());
    assertThat(firstMessage.getResponse().getStatusCode()).isEqualTo(500);`

I see that the newest version is 2.0.2 and I'm hoping it has the fix. But currently only 2.0.1 is available on Maven to insert into the POM file.

[t-o-n-y-p]

Hello, same thing here. Could you devs please push the fix to maven central? Thanks.

[shlmvgett]

Hi
The same problem is actual for us, could u update version on mvn repo?

[bp32891]

I did find a work around until they make a push. I created my on jar file from this repo and added it to my pom. Then I had to add more libraries but it now works. I no longer get the error message.

[Jonahss]

Sorry about the delay. I'll see about updating in Maven.

[valeo28]

Hi! Please uploade it to Maven Central.

[Jonahss]

Hi, I've been busy on my Wyldcard project, but thanks for poking me to update this. I'll see if I can do it on Monday.

[jlipps]

that's such a cool project dude!

[re-jim]

@Jonahss poke again, please update this.

[Jonahss]

I'm finally working on it :D
My credentials to Maven Central are no longer valid. I'm talking to the active Appium team to get access.

Thanks for pinging me, sorry for the delay.

[t-o-n-y-p]

Hello, how is the progress on this?

[Jonahss]

Hello. I think I have everything I need now. Will work on this today and tomorrow. Thanks again for pinging.

[Jonahss]

@t-o-n-y-p @re-jim v2.0.2 published to central repository.
Can you verify the code works as intended?

[t-o-n-y-p]

Unfortunately, I no longer have access to the environment to check it, thanks for publishing though :)

[Jonahss]

Ah, well, hopefully someone else can check. Or we'll hear about it here when it fails to work XD

…

On Wed, Sep 27, 2023 at 10:36 AM t-o-n-y-p ***@***.***> wrote: Unfortunately, I no longer have access to the environment to check it, thanks for publishing though :) — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALTRMKE3TVM3YFLCQCA4SLX4RPZ7ANCNFSM6AAAAAAXWAXJWE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[halilcifteci]

Hi, after upgrading my project, there was no problem. thanks @Jonahss

[Jonahss]

Yay! Okay, can close with confidence :D