Files

Lorenzo Blasa c45164ec2b Log unable to extract clientQuery as warning instead of error

Summary:
^
LogView is raising this up but I don't think there's an actionable item from our side. If a client doesn't have the right arguments on the query string then we effectively are unable to construct a valid query.

All our clients do this correctly, but there may be instances that either a browser or another process is 'trying' to connect to Flipper even if unintentionally. This behaviour I've observed in the past.

Changelog: Log 'Unable to extract the client query from the request URL' as warning

Reviewed By: passy

Differential Revision: D34340068

fbshipit-source-id: f5fc36a9803a83d6662b6383589bc0aa99774798

2022-02-18 05:50:07 -08:00

src

Log unable to extract clientQuery as warning instead of error

2022-02-18 05:50:07 -08:00

package.json

Bump dependencies in /desktop

2022-02-14 09:55:15 -08:00

README.md

Set up Flipper decapitated packages

2021-10-08 01:33:03 -07:00

tsconfig.json

Unshare global types

2021-12-17 07:36:07 -08:00

README.md

flipper-server-core

Package that manages connections with flipper clients, queries for adb/idb clients, accepts incoming websocket / rsocket connections and takes care of certificate exchange.

Used by Flipper desktop, flipper-server and flipper-dump