Failure : Pointing to local-omaha server

[Alonso Superuser]

I am not able to point the omaha-client to local-omaha-server.

After debugging through logs, I could find out that the "WinHttpAdapter::WinHttpStatusCallback" is called for "WINHTTP_CALLBACK_STATUS_CONNECTED_TO_SERVER". After that it is never called.
For Google Omaha Server, it gets called for "WINHTTP_CALLBACK_STATUS_SENDING_REQUEST", "WINHTTP_CALLBACK_STATUS_REQUEST_SENT" etc.

What could be the problem?

Thanks

[Ryan Myers]

Are you using HTTPS by default?

Your best bet, in roughly this order:

* Enable WinHTTP debug logging (use netsh winhttp on the command line) to see what WinHTTP itself is thinking

* In net\simple_request.cc, put a breakpoint on the call to winhttp_adapter_->SendRequest() and see what the return code is.

~rjm

--
You received this message because you are subscribed to the Google Groups "Omaha Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/omaha-dev/-/3O3j6iFweqAJ.
To post to this group, send email to omah...@googlegroups.com.
To unsubscribe from this group, send email to omaha-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omaha-dev?hl=en.

[Alonso Superuser]

Hey,

The problem was not WinHttp. It was the local omaha server. The server was expecting the http request with omaha-xml-tags. If the client directly sends that request then server responds well.

However, now I have the below problem ->

Local-Omaha-Server is not able to understand the http request of format :
http://10.204.22.153/service/update2?w=3:Ued7uk-Z8ilbdFRGiJ-nM1hmnZraateG8dc3VaJQbhT3NFvkUArV3VLPN0JujuF5VLTTszsiWgvfT3JJcHoUl5wLQiMPeFwEI-tHWLHOkholxUrUsqoFcEbEDFhIuhHuKvtH4qWXJPsPb2WP1lWXDywxXgPn7Oki3Ka9Lr5_tTk

What is above request?
I suppose it is the CUP protocol URL. Can I switch OFF the CUP-protocol?
What is the use of this request?

Thanks,
Shrirang

[Kp]

Hi Alonso,

I don't know whether this will help you, that if I debugged omaha-
client correctly then it refuses to talk to HTTPS server without a
valid certificate. This means that you have to use HTTPS server with
trusted certificate (You can self-sign certificate and make it trusted
by adding it as root certificate under windows) or you have to
implement CUP protocol.

I found simpler to use HTTPS

Best
Petr

On Sep 27, 10:43 am, Alonso Superuser <alonso.superu...@gmail.com>
wrote:

> Hey,
>
> The problem was not WinHttp. It was the local omaha server. The server was
> expecting the http request with omaha-xml-tags. If the client directly
> sends that request then server responds well.
>
> However, now I have the below problem ->
>

> Local-Omaha-Server is not able to understand the http request of format :http://10.204.22.153/service/update2?w=3:Ued7uk-Z8ilbdFRGiJ-nM1hmnZra...

>
> What is above request?
> I suppose it is the CUP protocol URL. Can I switch OFF the CUP-protocol?
> What is the use of this request?
>
> Thanks,
> Shrirang
>
>
>
>
>
>
>
> On Thursday, September 27, 2012 12:54:24 AM UTC+5:30, Ryan Myers wrote:
>
> > Are you using HTTPS by default?
>
> > Your best bet, in roughly this order:
> > * Enable WinHTTP debug logging (use netsh winhttp on the command line) to
> > see what WinHTTP itself is thinking
> > * In net\simple_request.cc, put a breakpoint on the call to
> > winhttp_adapter_->SendRequest() and see what the return code is.
>
> > ~rjm
>

> > On Wed, Sep 26, 2012 at 2:54 AM, Alonso Superuser <alonso.s...@gmail.com<javascript:>

> > > wrote:
>
> >> I am not able to point the omaha-client to local-omaha-server.
>
> >> After debugging through logs, I could find out that the
> >> "WinHttpAdapter::WinHttpStatusCallback" is called for
> >> "WINHTTP_CALLBACK_STATUS_CONNECTED_TO_SERVER". After that it is never
> >> called.
> >> For Google Omaha Server, it gets called for
> >> "WINHTTP_CALLBACK_STATUS_SENDING_REQUEST",
> >> "WINHTTP_CALLBACK_STATUS_REQUEST_SENT" etc.
>
> >> What could be the problem?
>
> >> Thanks
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Omaha Dev" group.
> >> To view this discussion on the web visit
> >>https://groups.google.com/d/msg/omaha-dev/-/3O3j6iFweqAJ.

> >> To post to this group, send email to omah...@googlegroups.com<javascript:>
> >> .

> >> To unsubscribe from this group, send email to

> >> omaha-dev+...@googlegroups.com <javascript:>.